Executing a test run

  Work in Jama > Work in projects > Test management > Test runs >

Executing a test run

Previous pageNext page Print this topic! Mail us feedback on this topic!

Executing Test Runs

Pressing the testrunplay button displayed in the front of each Test Run in a Cycle opens the Test Run execution window.

TestPlanExecution

Within the Test execution window are three content areas separated by tabs.

Test Execution Tab

The Test Execution tab allows users to execute the Test Run.

TestExecutionTab

Select Start test run to initialize the duration timer and enable the pass or fail buttons for the Test Run. To modify the duration of the test run, simply change the time of the duration and save. Users will be prompted to assign Test Runs to themselves when starting a Test Run if it's assigned to another user.

Note: If for some reason, you need to reset the Test Run to a status of Not Run, use the batch update Test Runs procedure to set the test run to Not Run. Or, you can unmark any steps that have been marked as pass or fail, and set the Test Run duration to 0. This will automatically reset the status to Not Run.

Once started, the Steps field in the execution window will add interactive pass and fail buttons to each step. If no steps were added to the original Test Case, a single pass or fail button will be included. A Result field is available to enter any relevant data, if necessary.

TestRunExecution

Users can mark a Test Run as blocked if there is something preventing them from executing all of the steps. Note that the "Mark as blocked" button is only available when at least one step have not been marked as pass or fail.
If one of the steps on the Test Run has failed but you want to pass the Test Run, the Force Passed button can be used. This button only appears once a step has failed.

TestRunExecutionForcePassed

Note: In order to see that this Test Run has been been passed with errors, you will need to configure your Test Run grid to see the Passed With Errors field.

If users discover a defect in their system when executing a test, they can use the "Log a Defect" button to quickly create a Defect. The location of where Defects are saved can be set under Project Configuration > Settings > Edit > Save Test Run Defects here. Defects created using the execution window will automatically create relationships to the Test Run.
TestExectutionLogDefects
You can edit the duration of the test run by double-clicking on the time and changing the time in the test execution window, or by editing the item and changing the time in the test run item view.

Note: You can prevent Defects from being created here by not configuring the Project Configuration setting.

 

In addition, you can attach a document to the Test Run by selecting Add attachment:

TestRunAttachment

These attachments will not be accessible from any Defect items created during the Test Run. Attachments or screenshots for a defect must be separately recorded on the Defect item.

Test Run Details Tab

This tab allows users to view the detail of the Test Run and its status. Customizing the view here is done by selecting the drop-down arrows next to the field type. By default the ID, Name, Version, Current Version, Last Modified By, and Date Created are selected. Choose to view as little or as much detail about the Test Run as needed.

The Test Case that the Test Run was derived from is displayed in this tab. Select the ID to open up a new window that displays the details of the derived item, such as, the goal of the Test Case, Pre-Conditions, and Steps in the case, and duration of test run.
Upstream items are shown in the this tab as well, making it easy to see what items are related to the Test Run. Simply select the item ID, and the detailed information about the related items pops up.

 

testRunDetailsTab

 

Test Case Tab

The Test Case tab displays details about the associated Test Case. This tab is read-only.

TestCasetab