Aborting Tests running within a Test Cycle
Before you read this you may want to see:
- Managing Test Cycles
- What is a Test Cycle?
- Edit/Update a Test Cycle
- Cloning a Test Cycle
- Deleting a Test Cycle
When should you Abort Tests running within a Test Cycle?
If you have scheduled tests within a cycle and you realize that tests are failing because you have a bad application build or deployment OR have a bad/incorrect data feeding into your tests and want to abort the execution of any further tests within that cycle, you may decide to abort tests within a cycle.
How can I abort tests running within a Test Cycle?
If you want to abort only a subset of the tests (or specific tests) running within a test cycle, you should use the QaCONNECT REST API or the Worksoft SaaS application to individually abort each of the tests you want to abort.
If your intent, instead, is to 'bulk' abort all tests that are scheduled, queued or currently in-progress, you should use the 'abort all currently running tests' feature at the test cycle level. This bulk-abort approach is a lot more efficient for you than individually aborting all the tests within the cycle.
There are two ways in Worksoft SaaS to abort currently running (queued, preprocessing in-progress, preprocessing completed and scheduled) tests of a Test Cycle:
- Manually using the Worksoft SaaS application
- Using QaCONNECT REST API
Follow the instructions provided below to abort currently scheduled, queued, or in-progress tests of a Test Cycle manually within the Worksoft SaaS application.
For the specific Test Cycle that you want to abort the tests from the Worksoft SaaS application from the Test Cycles listing grid, you can see the list of available options by hovering on the 'Abort' icon (that looks like a palm of a hand over a stop sign).
Below are the different options available for aborting the tests based on the needs which are shown on hovering on the "Abort" icon.
- Abort only Original Tests scheduled as part of this test cycle: On selecting this option, the original tests that are scheduled under a test cycle gets cancelled/aborted of the tests which are in either queued/in-progress states.
- Abort Original Tests and Auto Reruns by Worksoft SaaS A/ML of Flaky Tests that may be triggered in the future: On selecting this option will allow you to abort both the original tests and the auto re-executions which happen using Worksoft AI/ML feature.
To know more about the Auto Re-executions of the failed tests, click here. - Abort only Auto Reruns by Worksoft SaaS A/ML of Flaky Tests that are currently running or may be triggered in the future: On selecting this option will allow you to abort only the auto re-executions which happens for the failed tests using the auto-assignment of the Root Cause for Failure labels using AI/ML feature.
- Abort only Test Reruns triggered by Users: On selecting this option allows you to abort the tests that are manually re-executed by you or your team members within the project.
- Abort all Tests (including Auto Reruns by Worksoft AI/ML that are currently running or may be triggered in the future): On selecting this option allows you to abort any kinds of tests that are either original or re-executed (manually/AI/ML) which are either in-progress state of in the queued state.
On clicking on any of the options, you are prompted for confirmation, select 'YES' in the confirmation dialog for the Test Cycle to abort the tests within the selected test cycle.
