Good working Practices around Test Artefacts Reviews and Approvals
![]()
Hi,
We're looking at incorporating some good working practices around Test Artefact creation.
I want to be able to create a test plan
get the test plan reviewed.
create test cases.
review the test cases/approve
once review then create new test scripts.
But it seems that the process to review has to be post-child artefact review in order to set it to read-only.
For example if I wanted the Test Cases reviewed and approved before the creation on a test script I would then have to unlock the 'approved' test case to add a test script to it.
We are also going to have a rule which will link the Test Case 1 to 1 with test scripts so am I just being over zealous with the review and approve? Or can I link the Test Case review to the Test Script review.
Any general advice surrounding how people manage the review and approval process and when they 'approve' parent artefacts would be gratefully received.
I don't want to reinvent the wheel so are there some standard policies that most people employ?
Many thanks,
Dan.
|
Accepted answer
One other answer
![]()
Hi Dan,
Your QM process will either follow the default RQM process template and workflow or be customized for your Team/Department/Company. Sounds like you need to define a custom workflow. Paul Comments 1
Do people generally ensure the review/approval of a artefact before the start its child (Test Case/Test Script). Are there typical configurations (recipes) of workflows that most people follow.
I'm just wondering how people generally create their test cases and test scripts. Is there a way you can bundle up the review of the script with the test case?
Many thanks,
Dan.
|
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.