It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,908
×6,077
×1,381
×26
×11
×8

question asked: Oct 24 '13, 11:43 a.m.
question was seen: 5,624 times
last updated: Nov 06 '13, 1:20 p.m.

Related questions

FAQ - How this Forum works

How are you requiring approvals of test cases and test scripts?

1
Paul Spalitta (81●4●30●37) | asked Oct 24 '13, 11:43 a.m.
retagged Oct 25 '13, 2:29 p.m. by Laura Kuczarski (211●3●7)
Hello,

We setup the "Required Approvals" Precondition for Save Test Case, Save Test Script and Save Test Case Result however we ran into an issue with that precondition feature. The Required Approvals works for the first time an artifact goes through the state workflow; however, when an artifact is moved back to Draft, the "old" approval group in the Formal Review sectoin allows that artifact to be moved to the Approved state without requiring re-approval. I am wondering how other users are getting around this issue.

For us, we want to be able to reuse Test Cases and Test Scripts which means we want to force a re-approval on artifacts. If an artifact is moved back to Draft we want to force another approval. Right now, the old approval groups need to be manually archived to force re-approval.

We explored the concept of using Approval Trackings to control state transitions but unfortunately, artifacts can get stuck in the Under Review state if some precondition is not met when the Formal Review is completed.

Is anyone else trying to force approvals of artifacts? If so, what are you doing to force approvals for artifacts that were already approved and are being modified?

Thanks,

Paul

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Tory Jaskoviak (520●1●5) | answered Oct 24 '13, 1:04 p.m.
JAZZ DEVELOPER
Hi Paul,

From a best practices point of view, I wouldn't recommend re-using existing test artifacts once they have been approved.

From a design perspective, the 'Required Approvals' precondition is met as long as the specified number of users has reviewed/approved from the specified approval group. So as you encountered in your scenario, if you have already met that specified amount previously and then re-opened the test artifact, then it still contains the specified amount to be re-approved. The only way to get around this is to archive the review/approval group as you mentioned.

Another method I would recommend is rather than re-use the approved test artifact, simply duplicate it. When you duplicate, it will create a copy but without the reviews/approvals you had previously. This will allow you to create new approvals as you would expect to meet the precondition. More information about duplication and what is and isn't copied over can be found in the Info Center - https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.rational.test.qm.doc/topics/c_copy_overview.html&scope=null.

Regards,
Tory
Comments
Paul Spalitta commented Oct 24 '13, 5:00 p.m.

Hi Tory,

We have discussed the idea of duplicating test cases, as you propose and for the same purpose, but all the test leads & test managers here have unanimously rejected that idea since it only seems to increase the overhead of using RQM.

Our managers already complain about the overhead in using RQM, especially with regard to TER management. Duplicating Test Cases can only add to that burden. It also seems to create for us some issues in reporting and in project metrics.

Thanks,

Paul

Paul Spalitta commented Oct 28 '13, 1:22 p.m.

Hi Tory,


RQM is promoted as a system for test artifact reuse. Why advocate a concept (artifact duplication) in contradiction to that design theme? It seems that the Required Approval feature should be designed to work with the out-of-box artifact workflow which allows transitioning from Approved back to Draft.

Thanks,

Paul

0
permanent link
Lisa Caten (342●9●13) | answered Oct 30 '13, 1:06 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Short of changing how the preconditions and approvals work today, would it help at all to create a snapshot of the test case with it's approvals and then: delete the existing approvals, return the artifact to draft, and set up new approvals (which would then trigger the Required Approvals precondition? The initial approvals would still exist in the snapshot and the artifact history. Just a thought.
Comments
Paul Spalitta commented Nov 06 '13, 1:20 p.m.

Hi Lisa,


The issue with deleting (archiving) existing approvals is that the process is manually initiated. We need something that happens automatically. It would be nice if there were a precondition that automatically archived approvals when an artifact is moved back to draft.

Thanks,

Paul

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.