How to use TERs to support iteration test pass
Hello,
My small (10 people, geographically distributed) development team is determining how to move to RQM to track the test pass we perform at the end of each development iteration. Currently, we use a wiki page to track our manual testing. The page contains steps for regression and functional testing. The steps are intentionally vague to encourage the developers to follow slightly different paths through the product. To increase coverage of the variation points, we make sure each test is performed by at least two developers. Moving forward, we foresee having a test plan with test cases that cover the regression tests. Each iteration, test cases will be added for the functionality that was added during that iteration. We will use TERs to track our progress through the plan during each test pass. -- Is it possible to see only the test execution records for the current iteration? -- How do we see who tested a test case? Is this the owner of the test execution record? -- How do we capture that we want 2 people to perform a test case? How do we capture that it was covered by 2 people? We had planned to use multiple TERs, but RQM does not support multiple TERs for the same test script, test plan and iteration. -- Is there a way to indicate the parameters for creating TERs for a test script? For instance, is it possible to indicate that every time TERs are created, there should be one for platform X and one for platform Y? Thanks, Martha |
One answer
Hello, 1) Yes, you can see the TERs for the current iteration. You can do that by using the filtering support in the View TER list table. Unfortunately, RQM doesn't have the notion of a "current iteration" like RTC does. So when you create your query for the list table, you will have to specify the milestone you want to filter on. In RQM 3.0.1 you can actually save and share these queries, but you will still need to update the queries milestone each time you move to a new iteration. 2) The person who tested a test case is the owner of the Execution Result for that test case. You can see this from the View Test Case Execution Results page. Just filter based on the test case you are interested in and look at the owner field to see who ran the test case. 3) In terms of planning for 2 people to run the test case in the same iteration. Your situation is the first I've heard like this where the scripts are so vague, but it's interesting. You maybe able to use Test Suites for this. Essentially adding the same test case and test script to the Test Suite multiple times. But Test Suites don't provide a way for you to assign ownership to each test cases in the suite. So each tester would just have to know that he/she needs to run either one of the two test cases in the suite. At the end of the day, there will still only be one TER for both steps in the suite. So you couldn't report based on TERs to see that the test case is planned to happen twice. Instead you would have to report based on the Test Suite. I believe there are a couple of out-of-box Insight reports for Test Suites, but in general, reporting on suites is an area that RQM needs to improve. So you may just have to look at the View Test Suite Results list table to track progress. Or create your own custom reports. 4) I don't believe there is a way to enforce any rules when creating TERs. So for a given test case you can't force someone to create one for platform X and one for platform Y. It's up to them to decide what TERs they want to create. |
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.