Linking test runner and test listener using Lab ID

Owned by Arnaud David
May 04, 2020
3 min read

Overview

The test runner and test listener are linked by the Sealights server by use of the Lab ID.

The Build Session ID is used to identify the build that is being tested and need to be provided to the test listener as well. The test runner will attempt to get the Build Session ID according to an actively running test listener with the same Lab ID.

Note that the LabID need to be consistent throughout your pipeline.

Integration Build

In order to link several components in an integration build, they will all need to report the same Lab ID. For the integration build, the Lab ID will need to be created in the settings section of the Sealights dashboard.

  • The Application and Branch names should be the same as when reporting the integration build itself.

  • The Branch Name is used to specify different environments, like Dev, QA, Staging etc.

  • Sealights will always pass the latest reported BSID bach to the Test Runners for their provided 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

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

  2. The application server, with the test listener, is passing the Build Session ID (54rd67da-ab09-42d2) and the Lab ID (QA_ENV1)

  3. QA machine 1 and 2, with the test runners, are passing the Lab ID (QA_ENV1) and receiving the Build Session ID (54rd67da-ab09-42d2) from Sealights to link between the test listener and the test runner

Example of an integration build

  1. Application servers are each passing the same Lab ID and their specific Build Session ID:

    1. Tomcat #1 - Lab ID: integ_4356tr23cd and Build Session ID: 22cd54da-ab09-13d5

    2. Tomcat #2 - Lab ID: integ_4356tr23cd and Build Session ID: eh8267da-c40e-33e5

    3. Web server - Lab ID: integ_4356tr23cd and Build Session ID: 7urd27da-ag09-33e7 

  2. The test runners are passing the Lab ID integ_4356tr23cd and retrieving the integration build Build Session ID