Hey,
I am interrested in how to create a request in Groovy code and adding assertions to them. An example would be great.
> Yes and no. I have a class library where a create the requests and assertions which has made things so much easier, particularly with the assertions. With
> requests I sometimes still need to manually update test cases. An example of when I have to manually update each testcase is when a parameter is added and
> I'm adding multiple parent elements in the test case.
So you don't use Update definition on the interface? Why is this done manually?
> For the responses I have templates where I pass in the expected values. I use default values in many
> cases where an element is added, I've added global testcases.
What if the respons return a list which varies in size? Can the template handle that?
> There are also things I would do differently. I was quite new to SoapUI at the time and I'm a QA Engineer that knows how to code, not a developer.
Same here. If someone show me how to do it, or direct me where to find stuff - I can work it out.
But, in this area, the SoapUI documentation is lacking an overview. I guess it's all in the javadocs, but it's like looking for a needle in a haystack sometimes...
Thanks for your quick reply!
/magnus
