Forum Discussion
kgbheem
Occasional Contributor
well..
if you are not able to login then what would be the point of verifying other assertions and mark it as failed?
if i get 200 status then only i want to verify other things otherwise it should stop right there
Lucian
7 years agoCommunity Hero
This is not how this is supposed to be used. Normally you would have a couple of assertions based on which you would decide if a test step is passed or failed.
What you are looking for are conditional assertions which I didn't see before and for which I don't really see a good use.
Indeed you can be sure that a test fails just after checking one assertion but how does it hurt if all are checked especially when they are all evaluated in a blink of an eye?
What you are looking for are conditional assertions which I didn't see before and for which I don't really see a good use.
Indeed you can be sure that a test fails just after checking one assertion but how does it hurt if all are checked especially when they are all evaluated in a blink of an eye?
- kgbheem7 years agoOccasional Contributor
right.. i got your point but my client do not want to see more failure when the first assertion failed. so she is asking is there a method to stop it right after first assertion.
- TNeuschwanger7 years agoChampion Level 1
the only way i can think of is at testcase level where the groovy script step is in. From TestCase Options of the testcase (within 'basic' tab), tick the "Abort on Error" box which should stop the continuation of assertions maybe.
Related Content
- 2 years ago
- 11 months ago
- 8 years ago
- 4 years ago
- 6 years ago
Recent Discussions
- 22 days ago