Automated Rerun of Test Scripts

After a batch run has finished and it is found that some of the test scripts failed due to test environment issues, then it may be useful to rerun only the failed scripts, the predecessor scripts they depend on (Skip-on-prior-abort in Test Sets), and the non-executed scripts.

After such a rerun, all the test results from prior runs are consolidated with the rerun results. You use the Rerun button in the Test Execution view to perform reruns.

To rerun test scripts

From the Site Map, navigate to the Release screen, then the Test Execution view.
Select a Test Execution record, with a Status of Completed, that you want rerun.

Note that when a batch run is completed, the Test Execution record is updated as follows:
- A Reports zip and XML file are automatically created and uploaded to the Attachments applet of the Test Execution record.
- The Status of the Test Execution record automatically changes to Completed.
- The Rerun button in the UI is enabled.
Click Rerun in the Test Execution view.
- The Status of the selected Test Execution record changes to Requested.
- When a Siebel Test Execution job is invoked on the Jenkins server, the Test Execution record with Status of Requested is picked up and run on an available DISA client.
After the rerun completes:
- The rerun results are consolidated with that of prior runs, and the overall consolidated test results are uploaded to the Test Execution record.
- The Status of the Test Execution record changes to Completed.
- The Runs Completed field in the Test Execution record increments by 1. For example, the value in the Runs Completed field would be 2 after the first rerun completes.
- An XML file (with a <Runs Completed> suffix) containing a summary of the results is attached to the Attachments applet of the Test Execution record. For example:
```
<Test Run ID>_<Mastersuite Name>_MasterSuite_2<Runs completed>.xml
```
  You must select this attachment record to Create Test Passes - for more information, see Creating Test Results.