Forum Discussion
IMounsey-Smith
14 years agoOccasional Contributor
Hey thanks for your reply.
I ended up going down the 'easy' option way. Displays what I would like to see.
The second option you give would be an interesting case to set up. I wonder how loadUI/soapUI would handle it, if you had many simultaneous users set up.
I would imagine you would set up a testCase1 to generate the XML and store it into a datasink or a variable or some sort. Then another testCase2 that purely executes the request generated in testCase1 .
The only issue I see here is with the generated XML testCase and how the result is handled. I foresee that if you had 2 users executing the same test cases, you could get them overwriting each others generated XML. Then again this depends on how and where the generated XML is stored or used.
Interesting to see how it would work. Ill do some investigation and see if I can set it up.
I ended up going down the 'easy' option way. Displays what I would like to see.
The second option you give would be an interesting case to set up. I wonder how loadUI/soapUI would handle it, if you had many simultaneous users set up.
I would imagine you would set up a testCase1 to generate the XML and store it into a datasink or a variable or some sort. Then another testCase2 that purely executes the request generated in testCase1 .
The only issue I see here is with the generated XML testCase and how the result is handled. I foresee that if you had 2 users executing the same test cases, you could get them overwriting each others generated XML. Then again this depends on how and where the generated XML is stored or used.
Interesting to see how it would work. Ill do some investigation and see if I can set it up.