Forum Discussion
Lucian
Community 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?
kgbheem
6 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.
- TNeuschwanger6 years agoChampion Level 2
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
- 3 months agoarmygrad
- 9 months agoalinabond
- 3 years agoaeswaramoorthy