RQM Assigning New Test Scripts
I'm an RQM beginner as a disclaimer..
On a development project and we're using RQM to do testing. We're slowly learning and setting up RQM but we're trying to figure out how to assign test cases with multiple test scripts tied to them to a tester. Some of our test cases have 5-10 scripts associated and we want that whole block assigned to a given tester as a work item (tasklist). We are able to create the test case as a work item but when the tester views it it only shows the first test script in the block....and not the rest.
Any Ideas?
Is there some other way we should be setting this up....we just need away to be able to dish out blocks of test scripts to different testers?
Thanks ahead of time,
J
On a development project and we're using RQM to do testing. We're slowly learning and setting up RQM but we're trying to figure out how to assign test cases with multiple test scripts tied to them to a tester. Some of our test cases have 5-10 scripts associated and we want that whole block assigned to a given tester as a work item (tasklist). We are able to create the test case as a work item but when the tester views it it only shows the first test script in the block....and not the rest.
Any Ideas?
Is there some other way we should be setting this up....we just need away to be able to dish out blocks of test scripts to different testers?
Thanks ahead of time,
J
3 answers
On 7/14/2011 12:23 PM, jwakefield wrote:
You assign the ownership of executing a test case via the Test Case
Execution Record (aka TCER or TER). So you would want to create TCERs
for each planned test execution and assign them to the person how will
be executing the test case. You can create these and assign ownership
of these in bulk.
A limitation of TCERs is that you can't have more than one TCER for a
given test case, test plan, milestone and platform. Which means you
can't have a TCER for each test script in your test case. However, most
times we've found that customers have multiple test scripts in a single
test case for the wrong reason. And should really have multiple test
cases for each of their test scripts, then use a test suite to group
related Test Cases that they plan to execute together.
Separate TCERs are desired because RQM reporting on execution is driven
by TCERs, and since you can't have a different TCER for each test script
within the same test case, then you wouldn't be able to do planning and
reporting at the script level.
This page gives some guidance on when to use multiple test scripts in a
single test case, as opposed to using a test suite:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/c_testcase_overview.html
Also, this page discusses how to create and generate Execution Records:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/t_add_ter.html
I'm an RQM beginner as a disclaimer..
On a development project and we're using RQM to do testing. We're
slowly learning and setting up RQM but we're trying to figure out how
to assign test cases with multiple test scripts tied to them to a
tester. Some of our test cases have 5-10 scripts associated and we
want that whole block assigned to a given tester as a work item
(tasklist). We are able to create the test case as a work item but
when the tester views it it only shows the first test script in the
block....and not the rest.
Any Ideas?
Is there some other way we should be setting this up....we just need
away to be able to dish out blocks of test scripts to different
testers?
Thanks ahead of time,
J
You assign the ownership of executing a test case via the Test Case
Execution Record (aka TCER or TER). So you would want to create TCERs
for each planned test execution and assign them to the person how will
be executing the test case. You can create these and assign ownership
of these in bulk.
A limitation of TCERs is that you can't have more than one TCER for a
given test case, test plan, milestone and platform. Which means you
can't have a TCER for each test script in your test case. However, most
times we've found that customers have multiple test scripts in a single
test case for the wrong reason. And should really have multiple test
cases for each of their test scripts, then use a test suite to group
related Test Cases that they plan to execute together.
Separate TCERs are desired because RQM reporting on execution is driven
by TCERs, and since you can't have a different TCER for each test script
within the same test case, then you wouldn't be able to do planning and
reporting at the script level.
This page gives some guidance on when to use multiple test scripts in a
single test case, as opposed to using a test suite:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/c_testcase_overview.html
Also, this page discusses how to create and generate Execution Records:
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.test.qm.doc/topics/t_add_ter.html
Thank you for the response that was helpful.
I want to clarify one point you made, so I am sure that I understand.
RQM reports off of TCER. There can only be 1 TCER associated per Test Case....a 1 to 1 relationship. So if I want to insure that I have reporting down to the script level, I should only use 1 test script per test case.....and wrap up multiple test cases into a suite?
Does that make sense, and is it correct?
Thanks again for your help,
Josh
I want to clarify one point you made, so I am sure that I understand.
RQM reports off of TCER. There can only be 1 TCER associated per Test Case....a 1 to 1 relationship. So if I want to insure that I have reporting down to the script level, I should only use 1 test script per test case.....and wrap up multiple test cases into a suite?
Does that make sense, and is it correct?
Thanks again for your help,
Josh