Forum Discussion
timmer
13 years agoNew Contributor
M,
I am new to SoapUI so I don't know the correct name.
When I add a WSDL to the project it appears on the left hand side of the screen.
Each msg available for that WSDL appears under it, and I can send a request from there.
I am using SoapUI to help me determine how one of our vendors WS works, their WS is not very well documented.
There are no XSDs and the Requests and Responses contain CDATA with embedded XML. There are about 15 WSDLs,
some have upto 30+ messages, all using embedded CDATA. A few of the 30+msgs are completely generic and
support another 20+msgs ...
I do the following:
1. Run a Testsuite to login and capture the key to a project property.
2. Send a Request, check the status and capture the TrackingID
3. Run a Testsuite that sends out some commands, checks the status of the
project.TrackingId. If ready, get response data, if not loop ...
Step #2 is not done in a Testsuite because there are just too many commands. Maybe there is a
better way, but like I said I am a rookie with SoapUI. Manually copying the #2 TrackingId was
killing me so now I am using the RequestFilter.afterRequest Event.
Thanks,
Tim
I am new to SoapUI so I don't know the correct name.
When I add a WSDL to the project it appears on the left hand side of the screen.
Each msg available for that WSDL appears under it, and I can send a request from there.
I am using SoapUI to help me determine how one of our vendors WS works, their WS is not very well documented.
There are no XSDs and the Requests and Responses contain CDATA with embedded XML. There are about 15 WSDLs,
some have upto 30+ messages, all using embedded CDATA. A few of the 30+msgs are completely generic and
support another 20+msgs ...
I do the following:
1. Run a Testsuite to login and capture the key to a project property.
2. Send a Request, check the status and capture the TrackingID
3. Run a Testsuite that sends out some commands, checks the status of the
project.TrackingId. If ready, get response data, if not loop ...
Step #2 is not done in a Testsuite because there are just too many commands. Maybe there is a
better way, but like I said I am a rookie with SoapUI. Manually copying the #2 TrackingId was
killing me so now I am using the RequestFilter.afterRequest Event.
Thanks,
Tim
Related Content
- 8 years ago
- 9 months ago
- 2 years ago