Running Test stages in parallel using different Lab IDs

Owned by Eamonn O'Kane (Unlicensed)
Aug 14, 2020
2 min read

Overview

In some cases it may be required to run multiple test stages in parallel against the same application build. By using a unique Lab ID per environment the same application build can be deployed in multiple environments and tests run in parallel against them. The coverage from each environment will be reported separately on the Sealights dashboard using the environment Lab ID.

Supported Technologies

  • Java

  • Node.js

Limitations

  • In case the same Lab ID is used for for different builds of the same component running tests at the same time, the usage of Build Session ID in the test runner will need to be provided as well.

  • If the test runner is running before the test listener - The test runner need to be configured using the Build Session ID.

  • Sealights assume that an integration build is running against the latest running Build Session ID.

Example of a component build with 2 Test stages running in parallel

 

  1. The build machine is passing the Build Session ID (54rd67da-ab09-42d2)

  2. QA Environment #1 application server, with the test listener, is passing the Build Session ID (54rd67da-ab09-42d2) and the Lab ID (QA-ENV-1)

  3. QA Environment #2 application server, with the test listener, is also passing the same Build Session ID (54rd67da-ab09-42d2) with the different Lab ID (QA-ENV-2)

  4. QA machine Test #1 with the test runner is passing the Lab ID (QA-ENV-1) and receiving the Build Session ID (54rd67da-ab09-42d2) from Sealights to link between the test listener and the test runner

  5. QA machine Test #2 with the test runner are passing the Lab ID (QA-ENV-2) and receiving the Build Session ID (54rd67da-ab09-42d2) from Sealights to link between the test listener and the test runner

  6. When complete, review the Sealights dashboard for separate reporting of each environment tests