Comments on: Automated SOAP testing with maven and the SoapUI plugin

By: vinay

vinay — Mon, 28 Feb 2011 10:25:13 +0000

Soapui plugin unable to load the Classes defined in external groovy file. I have copied that script file into soupui script folder
I am getting below error.

15:45:02,306 ERROR [SoapUI] An error occured [startup failed: Script1.groovy: 1: unable to resolve class

By: Robbrecht van Amerongen

Robbrecht van Amerongen — Sun, 07 Mar 2010 19:55:03 +0000

The soapui-settings.xml file needs to be placed in your project root. Same location as your pom.xml.
Alternatively you can add to your soapui-plugin configuration.
Have a look at http://www.soapui.org/plugin/maven2/properties.html

By: Raj

Raj — Tue, 02 Mar 2010 20:36:12 +0000

Good article!
Is there a requirement that soapui-settings.xml file and the should be at the same level (directory)? And should the project file name end with soapui-project.xml?
when i have the projectFile in src/test/soapui folder, i am getting an error that the projectFile cannot be found.

By: Robbrecht van Amerongen

Robbrecht van Amerongen — Fri, 26 Feb 2010 15:05:04 +0000

The difference between these tools and the Oracle Specific tools:

- They are independent (not Oracle specific);
- SoapUI has a user interface that is easy to use, especially for non-oracle schooled testers;
- You can run and schedule your test independent of the Oracle infrastructure and make them part of your integrated build-infrastrucure;
- Soap-UI can simulate a proxy so you are able to test your ESB interface without “the other side” (not sure FTP has this);
- There are no costs involved. I do not know the exact licence structure of the Oracle tool.
- Reporting is more accessible for end-users.

By: Damien

Damien — Wed, 24 Feb 2010 11:11:16 +0000

Is there any real benefit difference in using these tools as opposed to using the file transport protocol and reporting feature of OSB itself? Each can achieve automated testing?