Running Tests against an Integration Build

Owned by Marc Amouyal
Last updated: Sept 07, 2021 by Oved Morad (Unlicensed)
1 min read

When executing tests against an integration build, you need to ensure the following mandatory configuration:

  1. A unique LabId was defined and common for all the components of the integration build

    • This parameter should be added to the startup of the Coverage Collector agent on the application (depending on the technology it can be added to the Javaagent, JS intrumented code, IIS settings…)

  2. When executing the tests you need to use the Build Session ID defined for the Integration Build together with the LabId

 

The common LabId ensures Sealights Servers will logically link Components with different Build Session IDs together for the Integration Build.

Because you can update only a single component (for example a single micro-service) for a new Integration Build - this method ensures you’re not forced to restart all the components with new parameters.