Running Tests in Parallel

This functionality is supported only if you are using the Open Agent.

You can use the command line to execute tests against mobile applications in parallel against multiple devices. This functionality is supported for both mobile web and native mobile applications, and can be used to run tests on physical devices, Android emulators, and iOS simulators. For example, you can use this functionality when executing test from a continuous integration server, or from Silk Central.

To enable parallel test replay, set the environment variable SILKTEST_ENABLE_PARALLEL_TESTING to true.

Note: Enabling parallel testing causes the Open Agent to handle each test-executing process separately. Applications which have been tested in one Silk Test client cannot be tested from another client, while the initial client is running. For example, you cannot test the same application alternating between Silk4J and JUnit.
Note: You cannot execute multiple test runs on the same mobile device at the same time. Before running tests in parallel, ensure that enough devices or emulators are available. Any test runs that get no mobile device or emulator assigned will fail.

Each parallel test run starts as a separate Partner process. Multiple processes starting simultaneously might each try to start the Open Agent on the machine on which Silk Test Classic is running. Running the Open Agent multiple times on the same machine is not possible and will cause Silk Test Classic to throw an exception. To avoid this, ensure that the Open Agent is running before starting the parallel test runs.

For example, you could start the Open Agent on the local machine by using the following PowerShell command:
powershell.exe -noprofile -command \"[System.Reflection.Assembly]::LoadWithPartialName('SilkTest.Ntf'); [SilkTest.Ntf.Agent]::Connect('localhost')
The test results are stored in multiple TrueLog files, one for each test run. To ensure that the TrueLog files are not overwritten, you can add placeholders to the TrueLog file name. For additional information, see Setting TrueLog Options.
Note: If you are experiencing high memory consumption during testing, ensure that test results are saved in the compressed TLZ file format, and not in the XLG format.