Integrations

To harness the advantages of Test Impact Analysis (TIA), ensure the following conditions are fulfilled:

1. Reporting test events to SeaLights, whether done automatically or manually (using the SeaLights Interface or Chrome Extension).

2. Automatically excluding tests during the upcoming test cycle based on SeaLights recommendations. This can be achieved by feeding this information to the test runner or by employing the SeaLights interface for manual testing.

You can achieve automatic reporting and test exclusion using one of SeaLights' official integrations or through the SeaLights TIA public APIs.

Test Framework Integrations

SeaLights currently provides integrations with a range of widely-used testing frameworks, including JUnit, TestNG, Cucumber, xUnit, nUnit, Mocha, Cypress, Jest, and Robot. For a comprehensive list of supported test frameworks, please reach out to your SeaLights representative.

Should you need integration with a new framework, please be aware that implementation timelines may fluctuate. Some integrations are relatively straightforward, while others may necessitate more time and effort to implement effectively.

API Integration

If you're working with a testing framework that is not currently supported by SeaLights, our platform provides public APIs to facilitate integration. These APIs enable you to capture test events, including test results, retrieve test recommendations for skipping, and force a full run during the next test stage execution.

For detailed information on utilizing these APIs, please refer to our API documentation.

Pull Request Integration

TIA currently must be manually activated for pull requests. Additionally, TIA does not consider the content of pull requests when refining its statistical modeling. This means that any changes in test behavior introduced in pull requests will not be reflected in the model until the pull request is merged into the branch and a new build is tested.