Feature Request:
Implement a comprehensive check versioning system to be able to experiment with multiple check description versions.
Parent Issue:
Previously, when a check suite was modified, the changes were immediately reflected in all test sessions (including completed ones). -> This bug was fixed.
Proposed Enhancement:
Implement a check versioning system that:
  1. Version Tracking
- Automatically create a new version when a check is modified
- Store version number and author of each change
- Maintain full history of all check modifications
  1. Allow version selection on single check reruns
- Allow viewing and selection of different versions for single-check re-run
- Ensure the execution details reflect with check version applied every time
  1. Audit Trail
- Track who made changes and when
- Provide changelog for each check
Use Cases:
  • Understanding test result trends over time
  • Debugging why results changed between runs
  • Rollback to previous check versions if needed
Technical Implementation Considerations:
  • Version storage strategy (separate table vs embedded documents)
  • UI for version history display
  • Version comparison tools