Page History

Create Test Execution Data

Using the Test Scripts you have already created, add them to the Execution Set folder for your Project, to do this you can: 

• In the tree, select a single Test Script or an entire Test Script folder from

You can add individual test scripts or entire packages of test scripts to a test execution package. To do this:

...

• the Script Library and drag it to

...

• your Test Execution folder.

Or

• From the grid, tick one or more check boxes to select Test Scripts, click the Create Execution button in the tool bar, select the destination folder.
  
  Image Added

The selected Test Scripts will The package/script and all its contents will then be copied into the destination execution package/ plan. You can also move scripts within the execution packages and plans in the same way by dragging and dropping.folder, ready for Test Execution.

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. 

To do this:

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.

Image AddedChanges made to an existing script in the script library will automatically update the corresponding script(s) in the execution set with the status of “Not Run”.  Current and historical runs will not reflect the new changes. A new run of a previously executed script will reflect the new changes.

Choose a Test Execution View

You can execute the steps for each test tests in a grid view of containing all steps, or in a single step view.

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

Multi Step Execution

...

To do this:

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

If you use Single Step Execution you run through a number of screens, one for each step, to complete the script.

1. Double Right click on the test to be executed.
2. Select the Single Step Execution tab.Type in the results, notes and select the status for the test step etc.
3. Click on ‘Save’.
   Image Removed

This section covers the running tests assigned to the execution set. From the script assignment you can view all information from the related script including: Script Description, Objects, Pre and Post Conditions, Notes and all custom fields.

Enterprise Tester provides a number of ways to run tests and you can choose to record your test results by using the single step mode or the multi-step mode.

You can start your test run in a number of ways:

...

...

1. All the details from the master test case in the Script Library are available while testing. In the title bar there is a link to the original master script/ test case in the Script Libraryrelated Test Script.  If you have permissions you can click on this link and update the script while execution the testthe Script or you can edit the Test Execution data directly which will update the Test Script automatically.
2. A stop watch feature is included for recording actual time spent testing. You can start and stop the time as requirerequired, close and come back to the run at a later time and start the time from where you left off.  You can activate the timer by clicking on the play button next to the Actual Time field.Image Removed
   

    

   NoteThe changes will only be reflected on the next test run and will not appear on the current run.
3. When you are running a number of scripts listed in the summary grid view, you can easily see how many scripts are left to execute when recording your test results. 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.
4. The Relationships tab shows all associations with this script run including the original master script Type in the script libraryresults, the requirement that the script covers and any associated incidents raised during testing.
5. The Run History tab shows the details of all previous runs including the version of the script used for the run.
6. Save and Next button allow you to move to the script on the list on your summary screen.

Edit Test Cases During Test Execution 

You can now edit Test Script information while you are executing a Test if the correct permissions are assigned.

Execute All Tests

1. notes and select the status for the test step etc.
2. Click on ‘Save’.
   Image Added

Ways to Start Test Execution

You can start your test run in a number of ways:

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

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

Image Added

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

Test Script Edit Image Added

If Test Execution Edit 

If a Test Script 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. 

The following fields can be edited during Test Execution if correct permissions are assigned and if the Test Script has not been completed.

Description, Expected Results, Data, Notes

Updated information will be saved to the related Test Script.

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

Filtering Tests

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

1. Expand the execution set to the package or plan containing the test scripts.
2. Double click the package/plan or right click and select view/edit package/plan.
3. Click on the Filter button and select the criteria to search/filter by.
4. Click on Search to filter records and display results.

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.

Image Added

How Test Script Changes Affect Test Execution

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.

Image Added

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.

Image Added

Historical runs will not be affected.

Relationships

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.

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.Image Removed