In almost all agile projects, functional testing starts as soon as you finish a story within an iteration and the code for it has been unit tested. This is when you will be using SoapUI.
Now that we have tested whether or not the functionality of the Weather Web Service works, we also need to include negative and boundary conditions. I will leave this to you as an exercise.
Just remember, create test suites and test cases, add assertions, and run the tests. We never even opened our favorite IDE. And to top it all, it was easy and fun.
We saw in this article how to use SoapUI to write functional tests. We tried to stay within the SoapUI itself. Coming up next week is what we do in any enterprise application. We want the user to log in, get a SessionID back, send this ID back in the Soap Header in all subsequent requests, and to log out successfully. This is just a scenario, but it is typical of what we do, right? Make a request, get something unique in the response, use this in subsequent requests, and so forth.
The next part in this series covers Groovy in detail, how to use properties, transferring properties from one response to another request, how to set global properties, and much more. Stay tuned.
Note: The SoapUI project file has been attached to this article. Opening this project we created is as simple as selecting the Import Project menu item and locating the place where you stored the downloaded project file. Give a yell if you are encountering any problems.