5.1.1: Adding Assertions Can Change Conditional GoTos

Hi,

Is the assertion part of the SOAP call or a separate Assertion TestStep. Either way adding an assertion should not change the configuration of your Conditional GoTo TestStep. Could you repeat the adding of the assertion and share screenshots of what is happening so we can look futher?

Thanks,

Giscard
SmartBear Support

Hi Girard,

Sorry for the delay in response.

Yes, the assertion is part of the SOAP call, and adding it does change the previous GOTO. This just bit me again this morning. In the screen capture, I added an assertion to the call 2 down from the highlighted one - 'Create App Setting Group Name Length' - I just tossed in an 'Assert for content' on one of the return lines, modifiedDateTime. When I went back to check the previous GOTO, I see that my TargetStep has been changed from the 'Create App....' call to the assert I just added.

You can see my conditional GOTO points to a step a few down, 'Create App...'


Now I add a random inline assert to that Create App step, to check for modifiedDateTime


Then I return to look at my GOGO - the target step has been changed from Create App to the new assert.

Hello,

I'm not able reproduce your issue in Ready! API. I would advise that you use Ready! API and see if you still have the same issue. If you still experience the same problem in Ready! API then please open a support ticket and send your project.

Support link, http://www.soapui.org/Support/support-overview.html.
Ready! API download link, http://support.smartbear.com/downloads/readyapi/.


Regards,
Marcus
SmartBear Support

Hi Marcus,

I'm sorry, I just don't have the time right now. I've no idea what Ready! is but I look forward to exploring it when I have more bandwidth. I guess just file this away in case someone else pops up with it - my conditional GoTo targets are definitely being changed to new inline asserts, every single time.

Thanks again,
Suzanne