Using the Test Scripts you have already created, add them to the Execution Sets folder for your Project, to do this you can by either of the following methods:
The selected Test Scripts will be copied into the destination Execution Set folder ready for Test Execution.
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.
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.
To do this:
Test Scripts can be copied from one project to another.
Execution Set data can only be created from Test Scripts within the same Project.
You can execute tests in a grid view containing all steps, or in a single step view.
To choose your default view, go to My Profile and update the Default To Single-Step Execution setting.
Multi Step Execution (Grid View)
Double click on the test to be executed.
Select the Multi Step Execution tab.
Single Step Execution
You can start your test run in a number of ways:
When performing Test Execution, you can automatically edit the following fields of a Test Script provided the correct Permissions have been given:
Permissions that will allow users to update Test Scripts during Test Execution are:
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.
To stop users from automatically updating Test Scripts while performing Test Execution:
Remove the Manage Executions Edit permission.
If Test Execution data is created where the status 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.
If a Test Execution window in mid-run is closed and re-opened, and if the related Test Script has changed in the interim you will be prompted to either continue or restart the run.
Historical runs will not be affected.
You can view Test Execution relationships from the Relationships tab.
Test Execution relationships are automatically inherited from the related Test Script, which may in turn have other associations.
If an Incident is logged during Test Execution, a relationship to that Incident is automatically created.
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.