Simple Deployment

About This Guide

Overview

Sealights allows you to collect code coverage and receive & execute for a .

A complete Sealights installation of a product involves three logical steps:

Scan the build artifacts of the application components that you would like to report to Sealights. Scanning the application components will help Sealights understand which code should be tracked for code coverage and changes.
Collect Code Coverage. In order to capture code coverage data & metadata from your application under tests while your tests are running.
Integrate into the test runner (test automation framework or manual runner). In order to indicate to Sealights when a starts and to get

In Simple Deployment, steps 1 and 2 happen together on the application under test.

Setup

Prerequisites

The following prerequisites have to be completed before starting the deployment:

Verify that you have an account in Sealights. For instructions on how to create an account, refer to the account creation page.
Onboarding requires DevOps or Admin permissions in the Sealights Platform. Please verify that you have the right permission.
Verify that the of the system under test and the machine(s) that run the test have connectivity to Sealights Cloud. See the How to verify connectivity guide for more information.
Installing Sealights requires modifying your application components' deployment scripts and possibly the CI Job that runs your tests. Please verify you have the necessary permissions in your organization.

Installation

Step 1: Agent Installation - Scan Artifact and Collect Code Coverage

The following steps are required in order to install the agent:

Create an (you'll need this token for the Sealights Agent configuration in step #3)
Create a (you'll need this generated identifier for the Sealights Agent configuration in step #3)
Download the Sealights Agent and configure your application to start with it. Detailed instructions on downloading and installing the agent will follow the notes below.

Note that the agent configuration step (step #3) must be repeated for each application component you want to capture coverage for.

When deploying an application component for the environment, do so from the same branch. This will allow Sealights to track code changes correctly for a given branch. Mixing branches for a single application component will lead to incorrect information.

Please select your backend technology to get detailed installation instructions:

Congratulations! At the end of this step, you can already capture coverage from your Manual Tests. Please follow these instructions to see how to do so.

Step 2: Integrate into the test runner

For integrating Sealights into your Test Runner (automated or manual), please refer to the Running Your Tests section in the documentation.

At the end of this step, you are able to see in the Sealights Dashboard the coverage for your tests (Manual and/or Automated), test results (success/failure), and potential savings via Sealights Test Optimization.

Validation

At the completion of the steps above, your application is set to provide coverage and get recommendations for the optimization of your tests.

Troubleshooting

In case one of the steps above did not succeed and you were not able to resolve the issue based on the logs, please contact Sealights Support for assistance.