> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/running-parallel-tests-lab-id/parallel-test-stages-unique-lab-ids.md).

# Parallel Test Stages (Unique Lab IDs)

<figure><img src="/files/anuNy3a1wWXjeOaNfeXf" alt=""><figcaption></figcaption></figure>

### Overview <a href="#overview" id="overview"></a>

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 <a href="#supported-technologies" id="supported-technologies"></a>

* Java
* Node.js

### Limitations <a href="#limitations" id="limitations"></a>

* 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 <a href="#example-of-a-component-build-with-2-test-stages-running-in-parallel" id="example-of-a-component-build-with-2-test-stages-running-in-parallel"></a>

<figure><img src="/files/Fp3LuEnhp046uQjPbqFY" alt=""><figcaption></figcaption></figure>

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/running-parallel-tests-lab-id/parallel-test-stages-unique-lab-ids.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.