Test run considerations for running tests on remote Docker hosts
Before you can configure a test to run on a remote Docker host, you must read the considerations that you must take into account.
You can run all the tests that are supported on Rational® Test Automation Server on remote Docker hosts.
Important: You can run stubs only in the Default Cluster location of Rational® Test Automation Server. You cannot run stubs on a remote Docker host.
When you plan to run any of the tests on a remote Docker host from a project on Rational® Test Automation Server, you must complete the following tasks:
Tasks | For information, go to... | |
---|---|---|
1.1 | Set up non-secure remote Docker hosts. | Setting up a remote Docker host computer |
1.2 | Set up secure remote Docker hosts. | Setting up a secure remote Docker host computer |
2 | Register the remote Docker host on Rational® Test Automation Server. | Registering a remote Docker host with IBM Rational Test Automation Server |
3 | Add a remote Docker host to the Rational® Test Automation Server project. | Adding a remote Docker host to the project for running tests |
4 | Configure a run for your test that you want to run on the remote Docker host by performing the following actions:
|
If you plan to run API Suites that use a transport and the transport requires third-party application Jar files for a successful run on a remote Docker host, then you must perform the following task:
- You must copy the third-party application Jar files to the third-party application folder on the computer where the remote Docker host is installed. See Copying third-party application Jars to a remote Docker host.
After you set up and register the remote Docker host with Rational® Test Automation Server, you can add the remote Docker hosts to your project on Rational® Test Automation Server. See Adding a remote Docker host to the project for running tests.