Hi,
we are using in this case a Delay-Step with 1ms 🙂 Easy and it works (Better a dummy request)
Hi,
we are using in this case a Delay-Step with 1ms 🙂 Easy and it works (Better a dummy request)
Yeah a delay might be a good choice as well but I was hoping for a different approach 😛
Hey LennSar, I've been looking into this and checking some internal resources but so far it seems like the only methods for 'forcing' a test case to stop involve it either being cancelled or failed. I'm waiting for confirmation as to whether or not this is possible or would need to be an enhancement request. Will let you know asap!
Unless I'm missing something, I don't fully understand why you make your goto statement go to a rest test step (<end test case dummy request>). mkrausem sugges a delay-step. I use in those cases a groovy test step.
So let to <finishTestCase> go to <end test case dummy groovy test step>.
You could even let the groovy test step log something like "Final test steps executed yes/no" depending on your condition (if you don't like dummy steps).
at the end it simply doesn't matter whether it's a rest call or a delay or a groovy script that I jump to. It's all the same approach which isn't my prefered way to begin with.
What I was hoping for was something like testRunner.finishSuccessfully or something like that but unfortunately there is no such thing....
