Page History

...

The selected Test Scripts will be copied into the destination Execution Set folder ready for Test Execution.

Test Execution data can also be created by dragging a single Requirement (that has Test Scripts associated to the Requirement) and dropping it directly into the Execution Sets folder or a Package within the Execution Sets folder.

Note: This only works if there are Test Scripts associated with the Requirement.

1. Ensure the Requirement has Test Scripts associated to the Requirement
   Image Added
   
2. Drag the Requirement (that has associated Test Scripts) into the Execution Sets folder or Package within Execution Sets folder.
   Image Added
   

   All Test Cases associated with that Requirement now have Test Executions visible under the Execution Sets folder or Package

   Image Added

Once Test Execution data exists in a folder, you can view information of the related script including: Script Description, Objects, Pre and Post Conditions, Notes and all Custom Fields. 

Organizing Test Execution Data

You can reorganize information within the Test Execution folders by dragging and dropping via the tree, or from the grid tick one or more check boxes to select Test Execution data and click the Move button in the tool bar, select the destination folder.

Where a large number of tests have been created within a single folder, it may be helpful to filter these records into more manageable groups. 

...

1. Double click the Execution Set folder.
2. Click on the Filter button and select the criteria to filter by.
3. Click on Search to filter records and display results.

Choose a Test Execution View

...

To choose your default view, go to My Profile and update the Default To Single-Step Execution setting.

Multi Step Execution (Grid View)

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 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 or Previous scripts by using the arrow buttons located in the top right corner.
9. Save and Next 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. 

Single Step Execution

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 or Previous scripts by using the arrow buttons located in the top right corner.
6. Type in the results, notes and select the Status for the test step etc.
7. Click on 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

...

• 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 and Attachments can be added at any time. 

Prevent Editing Test Scripts During Test Execution

...

Remove the Manage Executions Edit permission.

How Test Script Changes Affect Test Execution

...

If an Incident is logged during Test Execution, a relationship to that Incident is automatically created.

Run History

The Run History tab shows the details of all previous runs of this Execution data including the version of the Test Script that was used.