Step 5 (optional): Running Automated Tests
Overview
Automated tests are executed using software tools and scripts without manual intervention, providing efficient and repeatable verification of software functionality. By integrating Sealights into your automated tests framework, you will be able to see code coverage and test recommendations.
Integration Types
There are three Integration Types in Sealights:
Coverage Only Integration - Allows seeing code coverage for a composed of multiple application components (backend services and front end) for a single and . This type of onboarding is agnostic to the test runner. However, it doesn't allow a user to get Test Recommendations. See the collecting coverage guide for more information.
Deep Agent Integration - Allows you to onboard a composed of multiple application components (backend services and front end) for a single and . This type of integration provides code coverage and test recommendation; however, it requires that Sealights will support your test framework/runner.
Custom Integration - For scenarios where Sealights doesn't support your test framework but still wants to get code coverage and test recommendations, you can use our public APIs and create a custom integration.
Setup
Overview
The following section describes how to use a Deep Agent Integration, which allows you to onboard a composed of multiple application components (backend services and front end) for a single and . This type of integration provides code coverage and test recommendation; however, it requires that Sealights will support your test framework/runner.
Prerequisites
Scan and configure your application for code coverage collection. For more information, please refer to the Deployment page.
Verify that the machine(s) that run the test have connectivity to Sealights Cloud. See the how to verify connectivity guide for more information.
Know your automated tests setup. You need to know the following:
Which test framework is being used?
What is the command to run the tests?
Is there any customization that is being done to the framework
Installation
Configuring Deep Agent Integration results in our agent running as part of the Test Framework/Runner process. This allows the agent to hook to the relevant events and send test data & metadata to Sealights.
In order to ease the onboarding, we have created several plugins/integrations that will help you to configure the agent. In cases where an integration/plugin doesn't exist but your test framework is listed as supported, you can always revert to manually integrating an agent into a test process.
The following list contains a list of out-of-the-box integrations to our agent. When considering how to integrate, you must first consider the technology in which your tests are written. Once you know that, please search the list below for the relevant integration for the technology.
Java
.NET Core
.NET Framework
Node JS
Go
Other
Python
Verifying the installation
If the integration went as expected, you could validate that it worked by looking at the Sealights Dashboard and see:
Test counts - These should match the numbers you see in your CI. The only exception is in the Cucumber Test Framework, in which you can have more skipped tests showing, due to the way the agent classifies them.
Test Stage Coverage - if your test stage has coverage, it means your agent in the application under tests managed to connect to the agent in the test runner.
Further Reading
Test Optimization - Public API documentation.
Integrating Sealights into Gauge - a walkthrough describing how to write a custom integration to Gauge
Last updated
