How build notification unblocks test execution

When a fix for a defect is delivered in a build, IBM® Rational® Quality Manager automatically receives notification from the IBM Rational Team Concert build system and changes the status of test execution records (TERs) that are blocked to indicate that the tests are clear to run. This indication applies to both initial delivery of the code to test and to unblocking TERs that had been blocked by a defect.

The following workflow describes how test execution becomes unblocked when defect fixes are delivered to builds.

  1. A tester attaches a work item or a defect to a TER or a test case. This work item or defect must be resolved before testing can resume.
    1. When the work item or defect is attached to a single TER, that TER is blocked for execution.
    2. When the work item or defect is attached to a test case, all TERs that have been created for this test case are blocked for testing.
  2. A developer is assigned to the work item or defect, fixes it, resolves it, and delivers it to a build.
  3. When the build that contains the fix is completed and passes, a list of unblocked TERs that are ready to run is displayed on the dashboard.
  4. When the TER that was blocked is executed, the test execution result displays the build record of the build on which this test was executed.
If Rational Quality Manager is not integrated with an external build tool or if the user chooses not to depend on any build notification, the TERs or test cases become unblocked as soon as the associated work item or defect is resolved. The user can then execute the TER and manually specify a build record in the execution result.

Feedback