Requested by:
Zoltan F.
Request:
Better management and visualization of multiple test session executions with ability to filter and group by check suite or scope.
Current Behavior:
  • Re-run functionality exists at test session level ✓
  • Execution counter shows total check executions
  • Counter stays same if re-run with same scope (confusing)
  • No grouping or filtering by check suite
  • No grouping or filtering by scope (URLs/pages)
  • Difficult to track execution history
User Quote:
"Is it possible to manage the runs and re-run under the original session somehow like the test cases what could be executed many times but the test cases is still the same."
Desired Functionality:
1. Execution History Management
  • View all executions of a test session as a list
  • Each execution shows: timestamp, duration, results, scope changes
  • Link related executions together
  • Similar to test case execution history in traditional test management
2. Filtering and Grouping Options
  • Filter test sessions by check suite
  • Filter by scope (specific URLs or page types)
  • Group re-runs of the same test session
  • View execution trends over time
3. Better Execution Counter
  • Clearer indication of what the counter represents
  • Show number of times session was run vs total check executions
  • Historical execution count
Use Cases:
  • Track how a specific check suite performs over time
  • Compare results across multiple executions
  • Filter to see only relevant test sessions
  • Understand test session re-run history
  • Audit trail for test executions
Current Confusion:
User re-executed the same session but execution number stayed the same, leading to confusion about what the counter represents.
Status:
🔍
Discussion Needed
Team wants to hear more about this use case in upcoming sessions. New design may address some aspects.
Related:
  • Execution counter will be clarified/redesigned in new UI
  • New design may make current view "redundant"
Priority:
Medium - Workflow improvement for power users