Viewing Test Run Results

After your test run completes, you can inspect the outcome of each test within that run.

---

1. Open the Test Run Summary
   Click on the completed test run entry to open the Test Run Summary:

   

2. Explore the Summary Panel
   In the Test Run Summary, you can:

   1. Overview
      See a high-level summary of the entire test run (total tests, pass/fail counts, duration, etc.).

   2. Test Results
      View each test in the run along with its status.

      • Click a test name to view its logs.

      • If available, download the associated video recording for that test (see Test Run Settings).

      • Click Download results to download a JUnit XML report of every scenario's feature, status and logs for this run — useful for importing results into other test-analysis tooling.

        

   3. Log Information
      Access:

      • Logs for every test in the run
      • Test Kit logs (the Test Kit sets up the environment before tests execute - you may find these logs helpful for debugging test runs)
      • All available video recordings for the run
      • AireGlu logs, if the run used AireGlu (see below)

   4. AireGlu Logs
      If your tests invoked AireGlu, the AireGlu Logs tab shows what AireGlu itself recorded against the transactions your run used - endpoint invocations, task successes and failures, and their context.

      These logs are read from AireGlu at the moment you open the tab, and are never stored by AireAssert. That means they are subject to AireGlu's own retention: for an older test run, AireGlu may no longer hold them, and the tab will be empty.

   

Re-running failed scenarios

When a run has failed scenarios, the Test Run Summary shows a Re-run failed button with the number of failed scenarios. Clicking it starts a new run straight away. The new run includes only those scenarios and uses the same settings as the original run (browser, resolution, speed, concurrency, recording and timeouts). Its summary shows which run it re-ran.

• It works for finished runs and for aborted ones. An aborted run's re-run includes the scenarios that had failed before the run stopped, but not the ones that never ran.
• A failure in any row of a Scenario Outline re-runs the whole Outline.
• The re-run uses the current version of each feature file. If a failed scenario has since been renamed or removed, the re-run can't start and reports the missing scenario.
• You need permission to start test runs to see the button. Runs started before re-runs were supported show the button disabled.