Page History

...

1. Double click on the test to be executed.

2. Select the Multi Step Execution tab.

   
3. Type in the results and select the status for the test step.
4. Attachments can easily be added to each step.
5. Incidents can be added or you can link to an existing incident in Enterprise Tester or your external system.
6. In the title bar there is a link to the related Test Script.  If you have permissions you can click on this link and update the Script or you can edit the Test Execution data directly which will update the Test Script automatically.
7. A stop watch feature is included for recording actual time spent testing. You can start and stop the time as required, close and come back to the run at a later time.
8. The Run screen allows you to easily navigate to the next Next or previous Previous scripts by using the arrow buttons located in the top right corner.
9. Save and Next button buttons allow you to move to the script on the list on your summary screen.
10. Testers also have the option to change the status of all steps to Pass by clicking the Pass All button and click on Save.
11. The test execution will be saved. To view more information on the test step, click on the plus button to expand the individual steps to provide more information. 

...

1. Double click on the test to be executed.
2. Select the Single Step Execution tab.
3. In the title bar there is a link to the related Test Script.  If you have permissions you can click on this link and update the Script or you can edit the Test Execution data directly which will update the Test Script automatically.
4. A stop watch feature is included for recording actual time spent testing. You can start and stop the time as required, close and come back to the run at a later time.
5. The Run screen allows you to easily navigate to the next Next or previous Previous scripts by using the arrow buttons located in the top right corner.
6. Type in the results, notes and select the status Status for the test step etc.
7. Click on ‘Save’the Save button.
   

Ways to Start Test Execution

...

1. Double click Test Execution data on the grid.
2. Double click Test Execution data in the Explorer tab via the tree.
   
   
   
   .
3. Right click on the Execution Data and select either 'Run Script (multi-step)' or 'Run Script (single-step)' from the menu.
   
   
   
   

Edit Test Scripts During Test Execution

When performing Test Execution, you can automatically edit the following fields of a Test Script provided the correct Permissions have been given:

• Description
• Expected Results
• Data
• Notes

...

Permissions that will allow users to update Test Scripts during Test Execution are:

• Manage Scripts View and Edit
• Manage Executions View and Edit
• Execute All Tests / Execute Only My Tests

...

If Test Execution has been completed then users cannot update Description, Expected Results, Data, Notes and Status fields.

Actual Results data , Data and attachments Attachments can be added at any time. 

Prevent Editing Test Scripts During Test Execution

To stop users from automatically updating Test Scripts while performing Test Execution:

Remove the Manage Executions Edit permission.

How Test Script Changes Affect Test Execution

If Test Execution data is created where the status is “Not Run” is “Not Run” and the related Test Script is subsequently changed, your Execution data will be updated to reflect changes made in the Test Script.

...

If your Test Execution is mid-run, and the related Test Script is changed at the time the test is being run, your Execution data will not be changed automatically.  

...