Submitting defects during test execution

During test execution, you can create new defects or add existing defects and attach them to specific steps in a script. If your team has set up cross-server communication with IBM® Rational® Team Concert, you can file these defects and track their status right in Rational Team Concert.

About this task

To submit a defect during test execution:

Procedure

  1. Start the test execution process.

    You can execute tests in several ways, by simply running a test case, by running a test execution record, and so on. You can even run a test without a test script. In most cases, open the test asset, and click the Run icon (Run).

    When you are ready to file a defect, you can file a new defect or add an existing one.

  2. To add a new defect:
    1. Click the Add New Defect (Add new defect) icon to open the Add New Defect form.
      Note: To check for potential duplicate defects, click the Find Potential Duplicates (Find duplicate defects) icon. You can also move or copy a defect to a different project area by clicking the Move/Copy (Move/copy defect) icon.
    2. Complete the Defect form as needed.
      Note: The actual form may vary, depending on your defect provider.
      • In Summary, provide a concise description of the defect.
      • In Severity, select a severity level for the defect.
      • In Filed Against, select a category for the defect.
      • In Description, provide a more detailed description of the defect.
      • Assign a defect owner, priority, and due date.
      • Estimate the time required to fix the defect.
      • Enter one or more tags to identify the defect. Later, you can create queries that take advantage of these tags.

      The IBM Rational Quality Manager default defect template includes additional fields that are populated with information retrieved from the associated test case. If you use a different template that does not include these attributes, you cannot provide information for these fields:

      • Related Requirement: Supplies the requirements that are associated with the test case.
      • Related Test Case: Supplies the test case name that is associated with the test execution record.
      • Build ID: Supplies the build information from test execution.
      • Test Environment: Supplies the test environment that is associated with the test execution record.
      • Verification Point Failure: Supplies the name of the step in a manual test script in which the defect was opened.
    3. When you finish the form, click Save.

      The test execution window is displayed again, now showing the new defect that you just submitted.

    4. Click Stop to stop test execution.
    5. When asked to verify whether you want to stop test execution, click Yes.

      If you have established integration with Rational Team Concert, the defect owner can now view the defect in Rational Team Concert. When the developer opens the Links page for the defect, the test execution result is displayed under Blocks Test Execution, as shown in the following figure:

      Links page in Rational Team Concert work item

      By clicking the link, the developer can view the test execution page in Rational Quality Manager.

  3. To add an existing defect:
    1. At any point during test execution, click the Add Existing Defect (Add existing defect) icon to open the Add Existing Defect window.
    2. To search for an existing related defect, select Show related defects.
    3. To query a defect, select Show defects from query.
      Tip: You can create queries that group similar types of defects. For example, you can create a tag called triage, and then with a query, list all defects that contain that tag. The following list includes potential queries:
      • All defects owned by a particular developer
      • All defects planned for a particular milestone
      • All defects filed against a particular subcategory of the application under test
      • All defects assigned a high priority
      • All defects to be discussed at a daily or weekly meeting
    4. Select the Defect type.
    5. Use the defect ID or text from the defect to search for a particular defect.
    6. Select the defect, and click OK.
    7. Repeat steps 2d and 2e.
  4. If your team has set up cross-server communication with Rational Team Concert, and you filed a blocking defect, you can verify in Rational Team Concert whether the defect is still listed as blocking.
    1. In the Rational Team Concert Web interface, click Work Items.
    2. Under Shared Queries, expand Quality Management, and select the Defects blocking tests query. The defect is no longer be included in the query results.

Feedback