Tricentis SeaLights integration

Tricentis SeaLights (opens in new tab) is an AI-powered software quality intelligence platform that uses your application's code to determine which tests you need to run. When you integrate Tosca Cloud and Tricentis SeaLights, you get a few benefits that reduce the effort and cost of faster deployment:

• Skip tests that cover unchanged code to cut test cycle time.

• Focus only on relevant tests to troubleshoot and fix issues sooner.

Understand the integration

Tricentis SeaLights uses agents, which function as listeners. During the initial test run, these agents perform the following tasks: 

• Monitor the actions that your tests perform in your application.

• Connect these actions to your application code.

• Store this data.

When you run your tests again, Tricentis SeaLights knows which actions to expect and checks for changes in the code. If the code hasn’t changed, Tricentis SeaLights links the unchanged code back to the test that covers it and tells Tosca Cloud to skip that test. For detailed information on how Tricentis SeaLights works, check out the Tricentis SeaLights manual (opens in new tab).

Prepare Tricentis SeaLights

This section describes the base steps to prepare Tricentis Sealights for an integration with Tosca.

1. If you haven't yet, get Tricentis SeaLights (opens in new tab).

2. Set up Tricentis SeaLights agents as described in the Tricentis SeaLights agent manual (opens in new tab).

3. Note the path to the build session ID file. Your team will need it to enable the Tricentis SeaLights optimization for specific tests.

4. Create a Tricentis SeaLights agent token as described in the Tricentis SeaLights manual (opens in new tab). You'll need it to connect Tosca and Tricentis SeaLights. The agent token is sensitive information. Don't store it as plain text on your machine and transmit it only over secure channels, such as HTTPS or encrypted transfer tools, for instance. We recommend that you use secure storage mechanisms, such as environment variables or a secrets manager to protect the token on your system.

Set up the Tricentis SeaLights integration

Now it's time to connect Tosca Cloud to Tricentis SeaLights.

Before you start

To connect to your Tricentis SeaLights tenant, you need the following things:

• An administrator account for Tosca Cloud.

• The Tricents SeaLights agent token you created in step 4 when you prepared Tricentis SeaLights.

Set up the integration

Follow these steps to set up an integration between Tosca Cloud and Tricentis SeaLights:

1. Go to User menu > Settings > Integrations.

2. Select Set up integration on the SeaLights integration tile.

3. Paste your Tricentis SeaLights agent token in the text field.

4. Select Submit. The SeaLights integration is enabled.

Disable the Tricentis SeaLights integration

Follow these instructions to end the data flow between SeaLights and Tosca Cloud and remove SeaLights functionality:

1. Go to User menu > Settings > Integrations.

2. Find the Tricentis SeaLights integration, select Disable, and confirm the action.

Optimize test runs with Tricentis SeaLights

If you integrate Tosca Cloud with Tricentis SeaLights, Tosca Cloud skips tests that cover unchanged code based on the recommendation from SeaLights. This speeds up your test cycles and gives you more time to focus on the code.

Enable optimization

To enable the Tricentis SeaLights optimization for your tests, assign the following parameters to your playlists:

Parameter name	Value	Description
SeaLightsOptimization	True	Turns on the optimization in Tosca Cloud.
SeaLightsBuildSessionId	<Build session ID>	Defines which build of your application you're testing. Tricentis SeaLights uses this information to detect code changes. This parameter is required unless you're already using SeaLightsLabId . If both SeaLightsBuildSessionId and SeaLightsLabId are in use, SeaLightsBuildSessionId takes precedence. If you use this parameter, you don't need to use SeaLightsBuildSessionIdFilePath.
SeaLightsBuildSessionIdFilePath	<Path to the file with the build session ID>	Defines which build of your application you're testing. Tricentis SeaLights uses this information to detect code changes. If you use this parameter, you don't need to use the parameter SeaLightsBuildSessionId.
SeaLightsLabId	<Lab ID> You can give the parameter any value, such as myLabID or TestLabID.	Defines the Lab ID for your playlist. This parameter is required unless you use SeaLightsBuildSessionId. To use this parameter, a SeaLights coverage listener agent must also be running with the same Lab ID. If no agent is live, Tricentis Sealights will be disabled. If you also use SeaLightsBuildSessionId or SeaLightsBuildSessionIdFilePath, Tricentis SeaLights will prioritize those to make sure your test data links to the correct build.
SeaLightsTestStageName	<Test stage name>	Defines a test stage name for your playlist. Tricentis SeaLights uses test stages to track code coverage and test activity, for example integration tests, regression tests, or functional tests. The test stage name you define here will show up in SeaLights.