Stopping test runs

You might want to stop a test run or multiple tests that are running when you realized that you did not configure all the settings or you want to change a few settings for the test runs.

You must have initiated a run for one or multiple test assets from the Execution page.

You can stop either a running test or multiple running tests from the Progress page. You can stop the test if it is in either the In transition or Running state. You cannot stop the test run if the test has already completed its run.

Go to the Progress page and identify the tests in any of the following ways that you want to stop:
You can select the tests that satisfy the following conditions:
- The test must be either in the In transition or Running state.
- The Stop execution icon in the Actions column must be enabled for the test.
- The checkbox must be enabled for the test.

Perform the actions in the following table:


If...	Action...
You want to stop any test that is running	Perform any of the following actions: Click the Stop execution icon in the Actions column of the selected test. Click the checkbox in the row of the selected test, and then click Stop selected. The Stop execution dialog is displayed.
You want to stop multiple tests that are running	Perform any of the following actions: Click the checkbox in the row of the selected tests, and then click Stop selected. Click the Select all checkbox in the header row, and then click Stop selected. Note: All running tests are selected when you click the Select all checkbox. The Stop execution dialog is displayed.

Perform the following steps in the Stop execution dialog that is displayed:
1. Set the timeout period for stopping the test run. Enter a numeric value and select the unit from the options available as Seconds, Minutes, or Hours.
  
  The time out period is the time during which the test run is allowed to stop on its own and after the timeout period, the test is forced to stop abruptly.
  Important: If the timeout period is not set, a value of 30 seconds is considered as the default timeout period.
2. Perform any of the following actions:
  - Keep the Capture results option selected, if you want the results to be captured for the test.
    The captured results for the test are available to view from the Results page.
  - Clear this option if you do not want to capture the results.
  Note: The Capture results option is selected as the default option.
  
  Important: The results are always captured for API suites even if you clear the Capture results option.
3. Perform any of the following actions:
  - Keep the Execute 'finally-block', if present option selected, if you want the finally-block code in the test script, if present, to be run before the test run is stopped.
  - Clear this option if you do not want to run the finally-block code in the test script.
  Note: The option Execute 'finally-block', if present is selected as the default option.
  
  Restriction: The tear-down steps equivalent to the 'finally-block' code, if present in API suites are not controllable at test runtime. The Execute 'finally-block', if present option has no impact on API suites.
4. Click Stop execution.
A notification is displayed that the running tests are stopped.
Note: If the test run completes before you can configure the options for stopping the test run, a notification is displayed in the Stop execution dialog that the test asset has completed its run.

You have successfully stopped a running test or stopped multiple running tests. The stopped test runs are displayed on the Progress page with the status as Stopped by User. Stopped tests are not considered in the count of tests executed that are displayed on the Overview page.

You can re-initiate the test run from the Execution page or from the Results page by completing the configurations that you want for the test.

You can view the results or the execution log of the stopped test from the Actions column on the Progress page by clicking the Open action menu icon Image of the icon. .