Compare Executions Report

Test Run Comparison & Execution Diff in AXQA

Compare Executions allows you to analyze differences between multiple runs of the same test case. Instead of reviewing execution reports one by one, you can place them side by side and immediately identify what changed.

Why it matters

Helps detect regressions quickly.
Highlights changes in responses or validation outcomes.
Supports build-to-build comparison.
Provides clear visibility into behavior evolution over time.

What you can compare

Overall execution status.
Step-by-step results.
Validation outcomes (actual vs expected).
Response data differences.
Execution source and build references.

How it works

Select up to three execution runs of the same test case.
The system aligns steps in a structured comparison view.
Differences are visually highlighted.
You can clearly see which values changed and where.

Highlighting differences

The comparison view emphasizes changes between executions:

Changed response values.
Status transitions (e.g., passed → failed).
New or missing data.
Validation mismatches.

This makes regression analysis faster and more precise.

Common use cases

Comparing results between two builds.
Validating that a fix resolved a previous failure.
Investigating unexpected behavior changes.
Auditing repeated automation runs.

Best practices

Compare executions from different builds to track release stability.
Use comparison after applying fixes to confirm resolution.
Focus on highlighted differences rather than scanning manually.
Keep execution history organized for meaningful comparisons.

Common mistakes

❌ Comparing unrelated test cases
✔ Use comparison only within the same test case.

❌ Ignoring subtle data changes
✔ Review highlighted fields carefully.

Security & access

Only authorized project members can access execution comparisons.
Historical execution data remains unchanged during comparison.
Comparison does not modify any stored execution record.

AXQA

Did You Know?