(v2) 🚫Aborted Executions

You can find all the aborted test suite executions in the 'Aborted' tab.

A test suite execution may be aborted due to:

1. A user forcefully ending the execution.

2. The Qualitia Automation Studio Client or offline execution crashing.

3. The Qualitia Server services restarting.

4. Network failure causing a lost connection between the Qualitia Server and the Qualitia Client or Offline Package.

In the last two cases, the test suite execution continues without sending results to the Qualitia Server. When the execution is completed, you can import the locally saved results from the Suite of Suites screen. 

If a network failure occurs but connectivity is restored before the execution completes, the results will be displayed. The execution status will then show up in either the 'Completed' or 'Aborted' tab, depending on the execution status.

Viewing Aborted Test Suite Execution Summary Report

When you drill-down into an aborted test suite execution, the Suite Execution Summary Report and Test Case Iteration detailed report show the results based on the last update received.

Both screens display an 'Aborted' icon in the top-right corner. Hover over the icon to see why the execution was aborted if the reason is known, like a user forcefully terminating the execution, or a generic message if not.