Execution History & Regression Tracking in AXQA

Execution History in AXQA gives you a complete record of what was executed, when it was executed, how it was executed, and what the outcome was. It acts as the memory of your testing process — allowing you to trace every decision, validate regressions, and review past behavior with confidence.

Why it matters

• Provides full traceability across test runs.
• Helps teams understand what changed between executions.
• Supports regression analysis and auditing.
• Ensures accountability for manual and automated actions.

What is recorded

• Execution date and time.
• User or source of execution (manual, automated, or agent-based).
• Overall result (passed, failed, partially completed).
• Step-by-step outcomes.
• Associated build or version reference (if defined).
• Captured response data for API-driven steps.

Levels of history

Test Case History

Each test case maintains its own execution timeline. You can review every run individually, including detailed step results and validations.

Test Campaign History

When multiple test cases are executed together as a Test Campaign, the campaign records the sequence of execution and aggregates the final results.

How it works

1. A test case or Test Campaign is executed.
2. The system records structured execution data.
3. Each step’s outcome is stored separately.
4. The overall result is calculated and saved.
5. The execution becomes part of the permanent project history.

Why it’s designed this way

• To allow precise debugging of failed validations.
• To support comparison between different runs.
• To preserve historical accuracy even when test cases evolve over time.
• To maintain a clear separation between execution data and test definition.

Best practices

• Review execution history regularly during regression cycles.
• Use build references to organize results by release.
• Avoid deleting historical runs unless absolutely necessary.
• Leverage history when investigating recurring failures.

Common mistakes

❌ Focusing only on the latest execution
✔ Review trends across multiple runs.

❌ Ignoring execution source
✔ Consider whether a run was manual, automated, or agent-based.

Security & integrity

• Execution records are stored within the project workspace.
• Historical results remain preserved even if the test case is updated later.
• Access to execution history follows project-level permissions.

Related documentation

• Test Case Execution Report
• Test Campaign Report
• Compare Executions