Forum Discussion
Hi,
Yes, all that sounds relatively straight forward with SoapUI. A very simple starting point would be something like:
1) Create a Project, TestSuite & TestCase
2) Create new properties on the TestCase to store your work request id and invoice id
3) Create Request TestSteps to make the calls to the APIs of the two systems
4) Add Assertions to the TestSteps to verify the content of the responses
Is this sounding OK to you? Not sure, if this is exactly what you want or how much you already know about SoapUI, but I can obviously go into a lot more detail if required?
Regards,
Rupert
Awesome to know ! I played with SOAPUI before so I have some familiarity and what you are saying makes sense.
Where my curiosity/unfamiliarity comes in is at your 2nd point
- What if I do not have those IDs until after a service call is performed ? Are there properties that allow you to house and reference data that's generated from calls ?
- I want to be able to generate those IDs via service calls and then without me manually intervening take them for use in subsequent calls in the test suite.