SoapUI Runner

This project is a docker image for running functional SoapUI tests in a docker container. The image contains SoapUI 5.5.0 running on openjdk:8-jre docker image.

Usage

The basic structure for running SoapUI tests against the container is the following:

docker run -i --rm \
    -v <path_to_your_soapui_project>:/opt/soapui/projects \
    -v <path_to_your_output_folder>:/opt/soapui/projects/reports \
    robinmatz\soapui-runner:<tag> \
    -<soapui_options(optional)> \
    -I "<path_to_your_soapui_project>"

The docker run -i -rm command will run the container (-i argument), print the output on terminal and removes anonymous volumes associated with the container (-rm argument).

Since the container uses testrunner.sh as ENTRYPOINT, SoapUI CLI arguments will have to be specified. You can find a list of all supported arguments here.

Sample command

docker run -i -rm \
    -v ${PWD}:/opt/soapui/projects \
    -v ${PWD}/reports:/opt/soapui/projects/reports \
    robinmatz/soapui-runner:latest \
    -r -j -f /opt/soapui/projects/reports \
    -I "/opt/soapui/projects/sample-soapui-project.xml"

${PWD} gives you the current working directory. This is quite handy when running your tests in different environments, such as your local machine and CI-pipelines. The -r argument prints a small report on the console. The -j argument creates a JUnit XML report. The -f argument lets you specify the output folder of your test reports. Note that here you will have to specify the folder in the docker container. Last, the -I argument requires the path to the soapui-project.xml file. This path also refers to the path in the docker container.

Selenium Extension

If you run this image with the 5.5.0-selenium tag, you can execute Selenium scripts in SoapUI. For now, there is only the possibility to run Selenium scripts with Google Chrome and ChromeDriver.

The easiest way is to set the path to the chromedriver executable as a project variable in SoapUI. Then, in your script, use

System.setProperty(
    "webdriver.chrome.driver", 
    testRunner.testCase.testSuite.project.getPropertyValue("PATH_TO_DRIVER")
    )

When executing the script with this docker image, you can override this variable with SoapUI CLI parameter -PPATH_TO_DRIVER=/usr/local/bin/chromedriver

The above example will the look like this

docker run -i -rm \
    -v ${PWD}:/opt/soapui/projects \
    -v ${PWD}/reports:/opt/soapui/projects/reports \
    robinmatz/soapui-runner:5.5.0-selenium \
    -r -j -f /opt/soapui/projects/reports \
    -PPATH_TO_DRIVER=/usr/local/bin/chromedriver \
    -I "/opt/soapui/projects/sample-soapui-project.xml"

Troubleshooting

Chromedriver does not launch in container

In order for your Selenium script to run in the container, it might be necessary to set up your ChromeDriver with the following ChromeOptions

import org.openqa.selenium.WebDriver
import org.openqa.selenium.chrome.ChromeDriver
import org.openqa.selenium.chrome.ChromeOptions

def options = new ChromeOptions()
options.addArguments("--headless")
options.addArguments("--no-sandbox")
options.addArguments("--disable-dev-shm-usage")

def driver = new ChromeDriver(options)

Credit

Credit goes to

• Luka Stosic (lukastosic/docker-soapui)
• Daniel Davison (ddavison/soapui)