Re: SOAPUI Test case flow
Hi I'm looking for some best practices when creating SOAUI test suites. In the following data drive scenario whereby you can have multiple flavours of the same request in a test case and would lik...
Forum Discussion
Thanks for the reply again!
Ok, using a switch statement would be fine for requests purchaseProduct1 - to purchaseProduct3, however the 'other request1' should be executed after purchaseProduct1 - to purchaseProduct3 branch has been executed, the switch statement would not allow this there would still need to be a groovy script to go to the other request step. Also On the last iteration the flow would drop through all requests, so I have put the groovy exit step in to prevent this from happening. I can get this to function as required; I'm looking for a more efficient use of the soapui features to prevent a large number of steps in a given test case
Sorry my explanation is probably not the best, thanks again!
Christopher
Ok, using a switch statement would be fine for requests purchaseProduct1 - to purchaseProduct3, however the 'other request1' should be executed after purchaseProduct1 - to purchaseProduct3 branch has been executed, the switch statement would not allow this there would still need to be a groovy script to go to the other request step. Also On the last iteration the flow would drop through all requests, so I have put the groovy exit step in to prevent this from happening. I can get this to function as required; I'm looking for a more efficient use of the soapui features to prevent a large number of steps in a given test case
Sorry my explanation is probably not the best, thanks again!
Christopher