# Testing Frameworks Integration {% hint style="warning" %} This documentation page assumes the **two preliminary steps of scan and runtime instrumentation** for the application under test are **already completed**. {% endhint %} {% hint style="success" %} When your integration is successful, you’ll see * In Coverage Dashboard, the Test Stage name is associated with your application entry, detailing coverage and test results (passed, failed, skipped) * In the Test Optimization pages, for Supported Frameworks, you can see the potential and/or actual savings of your tests (including details on the recommendation reasons) for this specific application/branch/test stage. {% endhint %} ## Integration for Supported Testing Frameworks ### Built-in Integrations with other Tricentis Solutions
Framework nameDocumentation linkTest Optimization Support
Tricentis ToscaTosca - SeaLights integration
(Starting from Tosca 2025.1)
Tricentis qTestTricentis qTest - Sealights Integration
Tricentis TestimTestim Docs - Sealights Integration
### Integrations with the most common Testing Frameworks This document provides a tabulated summary of the integration support offered by SeaLights for various testing frameworks, categorized by the underlying technology and linked to their respective documentation pages or sections. For more detailed guidance on these framework integration processes, follow the documentation links provided in the table or refer to related sections within the SeaLights support documentation.
Framework nameUnderlying TechnologyDocumentation linkTest Optimization
Cucumber JSJavaScriptcucumber-js-framework
CypressJavaScriptCypress framework
Playwright JSJavaScriptplaywright-js-framework
TestCafeJavaScriptTestCafe Reporter
JestJavaScriptjest-framework
MochaJavaScriptmocha-test-framework
KarmaJavaScriptkarma-test-framework
AVAJavaScriptava-framework
ProtactorJavaScriptsealights-protractor-plugin - npm
RobotPython#robot-framework-sealights-custom-listener
PytestPython#running-tests-with-pytest
BehavePython#running-tests-with-behave
Cucumber JavaJava
JUnit, TestNGJava
SoapUIJavarunning-test-listener-with-soapui
JMeterJavarunning-test-listener-with-jmeter
xUnit.NET#running-tests-with-mstest-nunit-or-xunit
nUnit.NET#running-tests-with-mstest-nunit-or-xunit
MSTest, VSTest.NET#running-tests-with-mstest-nunit-or-xunit
Go TestGorunning-tests
GinkgoGo#using-ginkgo
Godog, Testify, GoConveyGo#framework-relying-on-go-test
### Integrations maintained by Third-Parties
Framework nameUnderlying TechnologyDocumentation linkTest Optimization
Katalon StudioJava
Ginger by Amdocs.NETGinger by Amdocs Help - Sealights Integration
## Generic Integration for Unsupported Framework ### Sealights Public API The SeaLights Public API provides integration capabilities with unsupported testing frameworks by allowing users to manage and optimize their test executions. Below are the detailed steps and API calls required for integrating Test Impact Analysis (TIA) using the SeaLights Public API: 1. **Creating a Test Session**: To begin a test session, you need to create a session using the dedicated API call. 2. **Getting Test Recommendations**: To optimize the testing process, you can retrieve a list of recommended tests to run and use them to dynamically reduce the list of tests executed 3. **Run Your Tests based on Recommendations:** Assuming your application under test is properly instrumented with Sealights 4. **Reporting Test Events**: Once tests are complete, report the test results with the timestamps for each test of its start and end time. 5. **Closing a Test Session**: Finally, close the test session (delete request) complete the testing cycle, and trigger the processing of all the related metadata (coverage and test results). {% hint style="info" %} All the relevant details of the API calls are described in our dedicated section of the portal: [Tricentis SeaLights Public API](https://api-doc.sealights.io/#9ca2b292-6f8e-4ee4-9221-a9f734ad9307) {% endhint %} ### Agents' legacy commands When using the legacy approach of a SeaLights Agent to run your tests, you can report and capture coverage and test results data effectively for your applications under test. The following steps are to follow: 1. **Start Session**: This command initializes a Test Stage Run for your build, which will be used to link all related test and coverage data. It's critical for associating results from different test stages. 2. **Run Your Tests:** Assuming your application under test is properly instrumented with Sealights 3. **Upload Results**: After executing your tests, you need to upload the test results (success, failed, skipped). 4. **End Session**: Conclude the session to finalize the data collection. This ensures that the session is properly closed and all related data (coverage and test results) is processed. {% hint style="info" %} This approach **doesn’t support Sealights Test Optimization** and will not allow you to skip irrelevant tests in a seamless way. If this is necessary, please refer to the Public API section. {% endhint %}
TechnologyDocumentation link
Java

#working-without-a-supported-framework

If you're using Maven or Gradle to trigger a testing framework that isn't directly supported by us but uses a supported test runner (like JUnit or TestNG) under the hood, please refer to the relevant integration guides above or contact Support for assistance.

Javascriptrunning-tests
.Net

#legacy-approach

If you're using a testing framework that isn't directly supported by us but relies on a supported test runner (like xUnit, NUnit, or MSTest) under the hood, please refer to the relevant integration guides above or contact Support for assistance.

Pythonno-supported-framework
Go#running-your-tests-with-the-legacy-approach