Manual Testing Versus BuildMgmt_ LabMgmt , TP,TC Lifecycles
Hi,
The project which I am supporting is mainly into Manual Testing and during one of the Training session I conducted have avoided the Build Management and Lab Management Sections just giving an overview as it is mainly related to Automation Testing.
But I got to know from some experts that Build can be used in RQM and so on .. Can anyone comment on this.
Another Suggestion was -- Do we have a Test Plan Lifecycle, Test Case Lifecycle, Test Script and Defect Lifecycle ?
Test Plan Life Cycle : Create a TP, Manage the TP with required Sections, Add related requirements , Test Cases etc.
Similarly for Test Cases : Create Test Case, Add Test Scipt etc
For Defect we have Work-flow defined in the process which consists of states and actions. I Could explain the different State Transition Matrix for that.
Based on the above inputs let me know if you have any better suggestions to help my team understand in a simpler way.
The main purpose is to make it as simple as possible for the project teams. Because by looking at different sections they are confusing them selves.
Regards
Anoop
The project which I am supporting is mainly into Manual Testing and during one of the Training session I conducted have avoided the Build Management and Lab Management Sections just giving an overview as it is mainly related to Automation Testing.
But I got to know from some experts that Build can be used in RQM and so on .. Can anyone comment on this.
Another Suggestion was -- Do we have a Test Plan Lifecycle, Test Case Lifecycle, Test Script and Defect Lifecycle ?
Test Plan Life Cycle : Create a TP, Manage the TP with required Sections, Add related requirements , Test Cases etc.
Similarly for Test Cases : Create Test Case, Add Test Scipt etc
For Defect we have Work-flow defined in the process which consists of states and actions. I Could explain the different State Transition Matrix for that.
Based on the above inputs let me know if you have any better suggestions to help my team understand in a simpler way.
The main purpose is to make it as simple as possible for the project teams. Because by looking at different sections they are confusing them selves.
Regards
Anoop
One answer
Hi,
There is a whole section about managing build in RQM in the online help, please see:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/t_verify_builds.html
Each test artifact type has a default workflow/lifecycle, with a state transition matrix which is fairly simple and linked to the review/approval process for those artifacts.
Regards
There is a whole section about managing build in RQM in the online help, please see:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/t_verify_builds.html
Each test artifact type has a default workflow/lifecycle, with a state transition matrix which is fairly simple and linked to the review/approval process for those artifacts.
Regards