Just wanted to know if there is any possibility in HP ALM [QC12] to have parent test case and child test cases?
I have a situation in my project where we have end to end scenarios... One test cases for the overall objective and there are 20 different application involved [20 teams to execute] say I need 20 individual test cases for each application and aligned in sequence of the flow. However I don't know how we can get the overall [status] objective of the End to End flow is completed/passed.
Tricky but there has to be some better way we can do this. Please throw some ideas...
Thank you for your response. But sorry I cant understand what you refer to parameterise Application.
How would that help me in having one test case at a parent level and other testcases in child level, and if all child testcases are passed the parent test cases should also be passed.
Can you please give a bit more clarity?? Appreciate your response.
I may have misunderstood your requirement;
If you have 20 test that are identical (the same flow/actions) and the only thing that changes is a few data elements (for example the name of the application), then you can create a test parameter for those data elements.
This will allow you to create configurations. Search the user guide for 'configurations' to read more about how to set them up and use them.
If you are saying that you have 20 different tests that you need to run in a sequence to complete one "test", then you have two options:
1. Create a single Test Set with all 20 test instances in it.
What you can then do is use the Execution Flow tab or to ensure the tests are executed in the correct order.
When you want to view progress you need to change your thinking a little bit: each test instance will need to be considered as a step, and the Test Set itself is a virtual test. If you want an automatic Pass/Fail/Not Completed status, then you'll need to implement some workflow code to automatically aggregate the status of the test instances up at the Test Set level.
2. The second option that I can think of is to use 'call to test'.
Each of your twenty tests will be a step in a parent test. Step 1 will comprise "Call to test: test 1"; Step 2 will be "Call to test: test 2".. etc.