Test Scripts and Test Cases relation
Hi,
We have planned to use RQM to centralize our tests. After some reunions, we have came to understand how to reflect our reality in RQM. But we have still difficulties to understand the link between test cases and test scripts. Here what I understand, a test case can contain multiple test scripts and a test script can be referenced by multiple test cases. A test script can be composed of keyword test scripts (inclusion). I noticed that if you try to execute a test case (or a test suite containing a test case) containing multiple manual test scripts, you have to choose one script. My question is what is the best way to reflect a case with some variations. So here is an example of my question: Test Case A - script 1 - script 2 - script 3 and create a test suite with 3 calls to Test Case A or Test Case A - Manual Script (includes script 1, script 2 and script 3) and 1 call I do not know if my question is clear. Thanks in advance. Robin, |
2 answers
A lot of times folks add multiple test scripts to a single test case for the wrong reasons. When instead they should have different test cases for each of their test scripts.
Folks often add multiple test scripts to a test case because at some level they related to a common function. For example, let's say my web based app has an Accounts Management page. You might have a script for adding a new account and one for updating existing account. So folks may create an "Exercise Accounts Management Page" test case that contains both of these scripts. I would consider this a wrong usage of a test case containing multiple scripts. If the user will always test these 2 aspects of the account management page together, then it would be best to have only one test script that performs both the add and update actions. If the user will some times test adding and other times test updating, then it's best to use two different test cases, each with their own respective test script. And if they ever want to plan to execute both of these test together, then use a test suite to group them. The only times so far that I've seen where it's appropriate to have multiple test scripts in a single test cases, is when the implementation of the test case may vary due to environment. So you may have one script that is specific to Linux and another that is specific to Windows. Also, a test case may have a manual script implementation and an automated script implementation using RQM's test script automation adapters (i.e. RFT automation). Less often I've seen some teams having different versions of a test script depending on the product version they are testing and the test case was shared between the test efforts of different product versions. Essentially, for a given test plan/milestone/environment, you should only need to run a single test script to consider that the test case has been executed. If you need to run more than one test script to consider that the test case has been executed, then you should create multiple test cases and use a test suite to represent the larger scenario that you need to execute. |
Also, a test case may have a manual script implementation and an automated script implementation using RQM's test script automation adapters (i.e. RFT automation). In our RPT/RQM integration, I added two types of scripts to each test case: 1. Manual test script, to describe the screen flow of a performance testing. 2. RPT script schedules. Jirong |
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.