Over the last year I had the opportunity to be involved in an Oracle SOA Suite 10g to 11g upgrade. At the starting point, the 10g situation, automated tests were not yet part of the landscape. As part of our approach to upgrade the SOA Suite from 10g to 11g, we created SoapUI tests to check that the 11g code would behave functionally the same as the 10g code. This ensured the quality of the code and it also enabled us to run a full regression test within 30 minutes. During the project we created around 300 test cases in SoapUI. Next to that we continuously leveraged our experiences while working in an upgrade environment, and improved our test approach during the project. In this blog I will elaborate on five best practices while using SoapUI in combination with Oracle SOA Suite.
1. Minimize groovy scripting.
As we made the SoapUI tests based on functional flows we realized that a large part of the SOA Suite projects are reused in various functional flows. To make the maintainability easier, we created some groovy scripts that handle the messaging for these steps. It shortens the number of steps in the test case by letting the groovy script handle multiple steps in the background. Also we would be able to store the groovy script in a scripts folder, and call it from any test cases we would create. See figure 1.
Figure 1 Using Groovy script to shorten the number of steps
It started out simple, with a few generic post and get message steps. But not long after that, the first if-then-else statements started to introduce themselves inside the scripts. After that started, the scripts gained in complexity. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.