RQM - Review
IBM.com Jazz.net Documentation Downloads developerWorks

A new version of this review page can be found at RQM-Review2.

Some tips tricks on Review.

When having multiple users as approver, all must approve before it's considered as a succesful aprovement. In other words it's an AND situation.

Figure: Progress can easily be checked.

Figure: Your open review tasks are visible on the dashboard.

A sample review setup in RQM404

The 404RC1 shows slightly different behavior compared to 403.

  1. Now available section "Associated E-signature"

A sample review setup in RQM403

This was tested on RQM 403.

In a more regulated environment an organization wants more control over the approval process. The approach described here might give you a jump start in configuring your process. This can be applied to:

  1. Test Plans
  2. Test Cases
  3. Test Suites
  4. Test Case Execution Results
  5. Test Suite Execution Results

Goals of this process:

  1. When review cycle is started, the artifact must be 'frozen'.
  2. When review is completed, state of artifact must be updated automatically.
Note! The pull down selector will jump back to TP after selection. Make sure you have the right identified.

With admin rights we define first auto-locks and un-lock rules:

  1. Select Manage This Project Area
  2. Select Test Artifacts
  3. Select Auto-Lock
  4. Select the Workflow to configure (e.q. the Test Case).
  5. To the Under Review add the Lock action.
    When a Test Case is put into "Under Review" it's automatically locked by the current user. This results that others can't change the artifact anymore. The approve/review cycle can be conducted.
  6. To the Draft state add the Unlock action.
    When a Test Case is put into "Draft" any autolock will be removed.
  7. To the Approved state add the Unlock action.
    When a Test Case is put into "Approved" any autolock will be removed.

Above takes care of the locking/unlocking when a review cycle is conducted. Be aware that the "Approved"-state is unmodifiable. Adding an auto-lock is UNWANTED (see warning below!).

By adding 'transition rules' an other level of automation can be added to the process. We add rules that if a review is resulting in pass (don't know an other word), than the artifact gets automatically the Approved state. If the review results in a fail (not good enough, work to be done), the artifact falls back to the initial Draft state without any lock.

We add the rule that in an Approved state, a review is changed from approved to rejected, the artifact will be re-opened (going to Draft). Hence there is a clearing UNlock on the Draft state, the autolock will be removed.

  1. Select Manage This Project Area
  2. Select Test Artifacts
  3. Select Approval Trackings
  4. Select the Workflow to configure (e.q. the Test Case).
    Check you've got the right Workflow (it jumps back to Test Plan when saving! - I've warned you)
  5. Add the 3 rules

The first rule defines: When an artifact (TC) is in the "Under Review" state and an approval process is executed and results in Approved, the artifact-workflow action "Approve" is executed, resulting the artifact into an "Approved" state.

Warning: When you add a Autolock to the Approve action you will end up with an artifact which can not be modified. Serious testing of your configuration is essential before putting into production.

Above can be complemented by the ruling that a Test Plan can ONLY be approved when the related Test Cases are approved.

  1. Select Manage This Project Area
  2. Select Preconditions & Follow-up Actions
  3. Select Save Test Plan
  4. Select Add
  5. Select "Disallow Transition to Approved until All Test Cases Approved"
  6. Select OK
  7. Select Save

You can contol the execution of test based on the state using these Preconditions & Follow-up actions. See the rules for "Execute Test Case".

Approve ALL

It might be tempting to request a "I want a approve all. By approving the ALL the artifacts related as child.". I'm against this option. That would 'kill' the approval process. An approval should be conducted thoroughly, otherwise it has no value. Especially when artifacts (Test Cases, Scripts etc) are re-used in various test activities. It's becomming to complex for a simple "Press Once, update ALL"....