Executes SoapUI load tests defined in a SoapUI project file. The xml file will be copied to the FD_TEMP_DIR and Property Replacement will be performed on the file.
Test Instance Properties
Property Name | Required | Description |
|---|---|---|
| Yes | Absolute path to the testrunner script (.sh or .bat) |
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|
...
Project Properties
Property Name | Property Code | Required | Description |
|---|
...
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Arguments |
| No | Arguments to pass Testrunner in addition to -r -f. |
| Project File |
| Yes | Path to SoapUI Project file. If a relative path is specified it will be relative to the FD_ARTIFACTS_DIR directory. |
Outputs
Output Name | Required | Description |
|---|
...
Artifacts
This operation doesn't consume or produce any artifacts.
...
Special Considerations
If you specify the –f -f parameter, the results will be copied to the location specified in a subfolder created at the time of the execution. This prevents the tests from overwriting each other, and organizes them by the time the tests were run for comparison purposes.
If you would like to turn down the logging in SoapUI, it is necessary to edit the soapui-log4j.xml on the testing instance. Change the section shown below from DEBUG to ERROR.
| Code Block | ||
|---|---|---|
| ||
<logger name="com.eviware.soapui"> <level value="DEBUGERROR" /> <appender-ref ref="SOAPUI"/> <appender-ref ref="CONSOLE"/> </logger> |
@since 5.4.0.3, plugin can process ReadyAPI LoadUI test results as well. In order for this to work, make sure that ReadyAPI is install folder contains word readyapi.