Forum Discussion
JMcKinley
17 years agoContributor
I did have one follow up question:
I haven't tried to implement your suggestion yet, but one of the things I want the system to do is show a failure for each test case... so, for example, if I create a "parent" test case that contains two "child" test cases so that I can pass data from one test case to another, and the first test case succeeds but the second test case fails, will the system show that the second test case fails? One of the reason I want to break up my test cases and pass data from one into another is so that we can see which parts of the system might fail.
For example (totally made up), lets say that test case 1 creates a record and succeeds but now I want to update the record so I want to pass the key from the create to an update test case. In a run of the suite (automated/unattended), the create works but the update fails. In this example, I would want to see that it was the update not the create that failed.
If I create the test case using the documentation you provided (thanks, btw!), is there a way to make sure that the system shows that it was the update test case that failed? My concern is that we would only see/get a message that it was the parent test case that failed... is there a way to make sure the system shows that the child test cases fail - not just the parent. Maybe it already does that by default OR if not, is there a way to do this?
Thanks again!!
Jim
I haven't tried to implement your suggestion yet, but one of the things I want the system to do is show a failure for each test case... so, for example, if I create a "parent" test case that contains two "child" test cases so that I can pass data from one test case to another, and the first test case succeeds but the second test case fails, will the system show that the second test case fails? One of the reason I want to break up my test cases and pass data from one into another is so that we can see which parts of the system might fail.
For example (totally made up), lets say that test case 1 creates a record and succeeds but now I want to update the record so I want to pass the key from the create to an update test case. In a run of the suite (automated/unattended), the create works but the update fails. In this example, I would want to see that it was the update not the create that failed.
If I create the test case using the documentation you provided (thanks, btw!), is there a way to make sure that the system shows that it was the update test case that failed? My concern is that we would only see/get a message that it was the parent test case that failed... is there a way to make sure the system shows that the child test cases fail - not just the parent. Maybe it already does that by default OR if not, is there a way to do this?
Thanks again!!
Jim