SeaLights - Preparation, Configuration, and Use

Owned by John Vanderzyden (Unlicensed)
Last updated: Mar 02, 2020
1 min read

This outline presents all the major steps for preparation and configuring SeaLights for use in your organization.

Preparation

As you prepare to integrate SeaLights with your environment, you must make these preparations:

  • The application build has been made ready for integration with SeaLights

  • Tests are available that can be run against the application

  • Connectivity is verified on the SeaLights dashboard for each machine on which the SeaLights agent has been installed.

Configure the build scanner

Next, you’ll need to add code coverage by configuring the build scanner. This involves:

  • Generating a token

  • Install and setup the appropriate agents and plug-ins on all participating machines.

  • Scan the application build.

Integrate Sealights with your build pipeline/process

Integrating SeaLights will require:

  • Configuring SeaLights to work with your CI/CD pipeline -OR- configuring SeaLights to work with your non-CI environment.

  • Capturing all key information about the applications and technical details for your environment.

  • Enabling user types and granting permissions to ensure the integration functions properly.

Add tests to the environment

To add tests, you’ll need to:

  • Install the test listener(s)

  • Run the relevant tests

Analyze Quality Risks

The goal is to discover the quality risks that are lurking in your untested code. Optimally, you want to find these risks upstream in your delivery pipeline—not in your production environment. With SeaLights Release Quality Analytics, you can automate the detection of such exposures and better enforce high quality standards throughout your organization. Learn more in Release Quality Analytics.