Running test case execution records

You can run tests several ways. One way is by running a test case execution record.

About this task

You can run a test case directly or you can run a test case execution record. When you run a test case directly, a default test case execution record is generated. But, the test case execution record does not specify a test plan, iteration, or test environment unless you select those optional values in the Run Test Case dialog box. If you want the predefined reports to reflect test results by test plan, iteration, or test environment, you can generate test case execution records before you run tests.

You create test case execution records in the context of a particular test case. Test case execution records map test planning and environment information to the test case. Therefore, when you run a test case execution record, you run the test in a specific test environment and associate the test run with a specific test plan and test iteration.

You can use test case execution records to run both manual and automated tests. If you create manual test scripts, you can add those test scripts to a test case and then add test case execution records to the test case. The same is true for any automated tests that you reference from Engineering Test Management. In many cases, when you run the test case execution record, you use a test script in a test case that is associated with the test case execution record.

To report on a specific build, you can create a shared query, where Build=build_record_name and Current for Build=true. You can use this query in dashboard widgets, such as Test Statistics, and Test Matrix.

The Current for Build flag for existing test case and test suite results will be updated by the asynchronous migration task. The Current for Build flag for new test case and test suite results will be updated automatically. To check the status of the Current for build flag on Test Case Results Migrator and Current for build flag on Test Suite Results Migrator tasks, go to https://server:port/qm/migration.

Procedure

  1. In an open test case, open the Test Case Execution Records section.
  2. Select the test case execution record to run.
  3. Run the test case execution record by doing one of these steps:
    • To run the test case execution record as is, click the Run icon Run.
      Note: If you use channels, the Test Case Execution Record runs on the first channel to which its Test Environment is related. View a Test Environment in the Test Environment Editor to view its related channels.
    • To choose a different test script to run, in the Test Script column, select the test script that you want to run. Then, click the Run icon Run.
    • To temporarily modify the values of execution variables, choose a build record to associate with the test case result, select records from test data, or pick a channel different from the default one. Click the menu arrow next to the Run icon Run and select Run with Options. In the Run with Options dialog box, select the options that you want and then click OK.
    The script execution view opens and an arrow points to the first statement.
    Note: If an automated test script is associated with the test case, select the appropriate adapter to run the test, and then click OK. The script execution view opens, and the test runs automatically. At the end of the test run, the adapter attaches the tool-specific result to the Result Details section of the test case result.
  4. For each step, follow the instructions in the step and then assign a verdict to the step.

    Possible verdicts include:

    • Pass Pass
    • Fail Fail
    • Inconclusive Inconclusive
    • Blocked Blocked
    • Error Error
    • PermFailed PermFailed
    • Deferred Deferred
    Note: To see the options for Blocked, Error, PermFailed, and Deferred, click the arrow next to the Inconclusive icon.
    Tip: To assign the same verdict to all steps that follow the current step, click the Apply All icon Apply all verdict.
  5. Optional: Type the step results in the Actual Results field.
  6. Optional: Add a comment to a statement:
    1. From the toolbar, click the Show/hide contents icon (Show/hide Contents). Make sure that the Show Attachments/Links box is checked.
    2. Click the Comment icon (Comment) in the column beside the active step to add, edit, and remove comments. The Comment icon is included with each statement that has a comment.
  7. Optional: Add an attachment to a statement. You could create a screen capture of the application under test and attach it to the statement. To attach a file to a statement:
    1. From the toolbar, click the Show/hide contents icon (Show/hide Contents). Make sure that the Show Attachments/Links box is checked.
    2. Click the Attachments icon (Attachments) in the column beside the active step to add and remove attachments. The Attachment icon and the attached file's name are included with each statement that has an attachment.
  8. If you discover problems with the application under test, you can submit a defect or link the active statement to an existing defect:
    1. From the toolbar, click the Show/hide contents icon (Show/hide Contents). Make sure that the Show Attachments/Links box is checked.
    2. To create a new defect, click the Create New Defect icon (Create new defect) in the column beside the active step. The Create New Defect form opens.
    3. To link a statement to an existing defect, click the Link to Existing Defect icon (Link to existing defect). Whether you create a new defect or link to an existing one, links to defects appear beside associated statements.
  9. When the test run is complete, click Show result to view the test case result.

    If necessary, you can modify the Actual Result and the weight distribution in the test case result. After you edit, be sure to click Save to save your changes.

  10. Optional: You can roll up the results of previous executions of the same test case execution record to create a new consolidated test case result.
    Note: You must have the Create Roll Up Result permission to roll up the results for a test case execution record.

    For more information about rolling up results for a test case execution record, see Rolling up results for test case execution records.

What to do next

If your organization requires a review of the test case result, you can use the Formal Review section of the test case result to assign reviewers and approvers.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki