How are you requiring approvals of test cases and test scripts?
![]()
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
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.