Closing (Marking Complete) a Test Cycle
Before you read this you may want to see:
Main Article
Once all the automated tests that you intended to get executed within a Test Cycle have been completed, you should mark (record) the completion of that cycle. In Worksoft SaaS, this is also referred to as 'Closing' a Test Cycle.
When can you close a Test Cycle?
You will only be able to mark complete a test cycle when there are no tests that are currently scheduled, queued or in-progress state within that cycle.
If you do have within a cycle some tests that are scheduled, queued or in-progress state and you will NOT be allowed to close a cycle. You will have to wait for all tests in that cycle to reach their final state of completion or abort before you can get your request to process successfully. (Or if you choose to, you can abort the currently pending/processing tests first (using either the Worksoft SaaS application OR QaCONNECT REST API), and then proceed to close the cycle.
Once you mark complete a test cycle, any test execution requests you make through QaCONNECT REST API that include/tag the run to the closed test cycle will NOT be picked up for execution.
How can I close a Test Cycle?
You can close or mark complete a Test Cycle in Worksoft SaaS manually using the Worksoft SaaS application or using QaCONNECT REST API.
To know how to close through QaCONNECT REST API, click here.
Follow the instructions provided below to 'close' or 'mark complete' a Test Cycle manually within the Worksoft SaaS application.
For the specific Test Cycle that you want to close from the Test Cycles listing grid, click on the 'close' icon ( that looks like a notepad with a red crossmark).
When prompted for confirmation, select 'YES' in the confirmation dialog for the Test Cycle to closed/marked complete.