Which Test Cases have been reviewed?
This question would apply to Plans/Suites/Scripts too but I'm struggling to find a way to lets me view which test cases have been reviewed.
- Reviewer(s)
- Reviewed State
- Approver(s)
- Test Engineer (TE) writes the initial Test Case draft
- TE adds Reviewer(s) to test case -> Design Engineers
- TE adds Approver(s) to test case -> Myself
- TE changes the state to "Ready for Review"
- Design Engineer adds comments and marks either "reviewed" or "Rejected".
- TE incorporates or rejects feedback.
- Approver goes in to approve or Reject
Accepted answer
Hi Tom,
As of now, the only way to make sure the QM artifacts are reviewed/approved upon is by using the formal review process and setting the condition where in once the approver after approving approves , automatically change the state of the artifacts to Approved. This can also be tracked via the history of the artifact.
Currently there are no out of the box facility available for the end user to look for these columns where the artifact is in the states mentioned below. However, I suggest you try creating global categories with these names and make these categories mandatory so that user undergoing the review process needs to fill the data under these categories and can also add these custom categories as columns while browsing the test artifacts.
- Reviewer(s)
- Reviewed State
- Approver(s)
Global Categories Info :https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.test.qm.doc%2Ftopics%2Fc_organize_with_categories.html
Hope this helps,
Krupa
Comments
Krupa,
3 other answers
We went about resolving this problem in a different way. We changed the workflow so that it was like this:
Key: (State) [Action]
(Draft) [Ready for Review] > (Awaiting Review) ... development complete but not yet submitted for review
[Initiate Review] > (Under Review) ... formal review initiated (i.e. emails sent)
[Approve] > (Approved) ...obvious
[Reject] > (Reopened) ... instead of going back to draft where it would be indistinguishable from before being reviewed
The actual workflow we have implemented is a little more complex, defining the various allowed state transitions, but it illustrates the solution to the original poster's question. I just wish that RQM came out of the box with a more workable workflow (the default is far too simplistic), rather than us have to invent our own and have to propagate the workflow to all the other artifacts.
However, there doesn't seem to be an obvious way to automatically trigger the [Initiate Review] action as a result of raising a formal review. My colleague has raised this question as a separate article on the forum.
