SeaLights
Also known as: Tricentis SeaLights, SeaLights for ABAP
SeaLights is Tricentis software that maps an application’s code to the tests that exercise it. A build scanner and test listeners feed that map, which SeaLights uses to select tests after a change. Software delivery teams use its coverage reports and quality gates to catch untested changes before promotion, and the ABAP offering gives SAP teams the same link from a transport to the tests that cover it.
SeaLights is a quality intelligence product that Tricentis bought in July 2024, nine years after the company was founded. It connects a change in the codebase to the tests that cover it so a team can see what a new build actually needs to verify. A Build Scanner analyzes changed code and a Test Listener follows executions in the team's existing test tools, manual and end to end runs included. SeaLights combines their inputs to identify which methods or objects individual tests exercise.
It can collect coverage for different test stages and across technology stacks including Java, JavaScript, TypeScript, Go, Python and .NET. Parallel execution environments can carry separate Lab IDs so their coverage remains distinguishable. Test Gap Analysis finds changed code that no test exercises, and User Story Coverage maps those gaps to the business features they touch.
Test Impact Analysis uses the resulting map to select tests affected by a change. It can also include previously failed, new and pinned tests, and a team can periodically run its entire suite. In a connected Testim project, SeaLights returns the tests that can be skipped for a build and Testim excludes them from the run. Tosca Cloud can do the same with supported executions.
SeaLights has application and account defaults for Quality Gates, with mandatory thresholds for coverage of changed code and optional thresholds for total coverage and test failures. A build can show missing data or a scan issue separately from failure against a quality threshold. The result can control whether a release pipeline promotes a build or blocks a change too risky to merge.
Tricentis sells SeaLights through a product specific demo and sales process. An organization operates a SeaLights account and runs instrumentation in its own build and test environments. The coverage service runs as hosted software. SAML 2.0 single sign on maps identity provider groups and roles to application access, and group scoped API and agent tokens separate machine access from user access.
SeaLights is within the scope of Tricentis's annual SOC 2 Type II audit and its ISO 27001 and ISO 27701 certifications. The product also provides a REST API and an MCP server the customer runs in Docker or as a command line process. Its cockpit tools manage the scanners, listeners and labs and read the audit log, and its coverage tools return results by application, branch and build, so an AI coding assistant can check what a change has been tested against.
A custom application team can combine coverage from unit, integration and end to end tests in one release workflow, while an SAP team can use SeaLights for ABAP to connect a transport in ECC or S/4HANA to the tests available across qTest, Tosca, OpenText ALM, Xray and other repositories. A global gaming company using SeaLights and qTest reduced production defects by 90%, accelerated releases by 80% and reached coverage of every code change. A cybersecurity company cut its integration suite from 30,500 tests to 4,900 and reduced its CI cycle time by 88%, and a financial services platform cut its regression scope by 70% and caught 100 critical gaps before release.
Vendor details
Canonical URL
https://www.tricentis.com/products/quality-intelligence-sealights
Category
SRE / DevOps agent
Subcategory
Test impact analysis and release quality gates
Company status
acquired
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Tosca Cloud, Testim and CI pipelines can use test selection. SeaLights for ABAP draws on Tosca, qTest, OpenText ALM, SAP Solution Manager, Certify, Xray and Excel. REST and MCP expose quality data to other tools.
In practice
A release engineer configures a minimum changed code coverage threshold for a service and makes the build promotion step depend on the gate result.
A Testim team ties a regression run to its SeaLights build session so changes to one component do not rerun the entire browser suite.
An SAP team reviews an incoming transport, runs the tests linked to the changed ABAP objects and sees which objects are still uncovered.
Sources & related URLs
Related / legacy domains
Research sources
Agentic Index coverage score
9.0 / 14 capabilities · 64%
| Integrations & Tool Calling | Full |
|---|---|
|
SeaLights uses an agent token to connect its test optimization service to a Testim project. When Testim sends a list of candidate tests for a build, SeaLights returns which ones to skip and the execution process excludes them automatically. Tosca Cloud also uses its optimization result to skip tests. Connected runners keep their own test definitions and execute the selected subset. Sourcedocs.tricentis.com/testim/content/integrations/sealights-integration.htmread 2026-11-20 |
|
| Workflow Orchestration | Full |
|
Build Scanners and Test Listeners divide the work of collecting code changes and observing test activity. SeaLights joins their results before deciding coverage and evaluating pipeline checkpoints. A single workflow can include observations from parallel environments under distinct Lab IDs. A build promotion step can consume the decision after the checks complete. Sourcedocs.sealights.io/knowledgebase/guides/quality-improvement/technical-overview/technical-architectureread 2026-11-20 |
|
| Knowledge Grounding & RAG | Full |
|
A persistent mapping connects code changes to specific tests and tracks coverage across builds and test types. The Build Scanner adds information about changed code and the Test Listener captures what each existing test exercises. For SAP, the same approach links objects in a transport to tests from several repositories and identifies the changed objects that lack coverage. Sourcetricentis.com/products/quality-intelligence-sealightsread 2026-11-20 |
|
| Human Oversight & Guardrails | Partial |
|
Release teams can set minimum changed code coverage, select whether to count all failures or the latest result for each test, and apply defaults or application overrides. The quality decision can stop a build promotion when the thresholds fail. A person sets the conditions and reviews the gate result. The check enforces those conditions without a separate approval queue. Sourcedocs.sealights.io/knowledgebase/settings/quality-gatesread 2026-11-20 |
|
| Security, Identity & Governance | Full |
|
Tricentis includes SeaLights in its annual SOC 2 Type II audit and in the scope of its ISO 27001 and ISO 27701 programs. SeaLights supports SAML 2.0 single sign on with separate user, administrator and DevOps roles. Group membership controls which applications a user or machine token can access. Administrators can rotate or revoke tokens in the SeaLights tenant. Sourcetricentis.com/trust/securityread 2026-11-20 |
|
| Observability & Auditability | Full |
|
A Quality Gate result breaks out each configured threshold beside the actual measured value and shows which requirements passed or failed. The coverage report distinguishes a failed threshold from a missing test stage, no detected changes and a build scan issue. Engineers can use that report to reconstruct which inputs and rules produced a build's release decision. Sourcedocs.sealights.io/knowledgebase/settings/quality-gatesread 2026-11-20 |
|
| Memory & State Persistence | Not documented |
|
A release analysis compares the current build with a selected reference build, and the coverage calculation uses the tests run against the current build. Prior builds can be selected as a baseline and retained as part of the project's records. Those records are the quality portfolio and do not form a separate memory layer with its own retention settings. Sourcedocs.sealights.io/knowledgebase/settings/quality-gatesread 2026-11-20 |
|
| Deployment & Data Residency | Not documented |
|
The SeaLights analysis service is hosted. Customer environments run the scanner and listener that collect build and test evidence, then send information to the SeaLights account. Tosca optimization uses Tosca Cloud execution. The installed collector and customer operated MCP server leave analysis in the hosted service and do not provide a private analysis deployment. Sourcedocs.tricentis.com/tosca-2026.1/en-us/content/sealights_integration/sealights_integration_overview.htmread 2026-11-20 |
|
| Prebuilt Agents / Templates / Packs | Partial |
|
An account starts with predefined Quality Gate settings, and a customer can tailor them by application or use a single organization default. The product includes scanners and listeners for different application frameworks and test runners. Customers combine those components with their existing release pipelines, with the defaults setting initial thresholds for one workflow. Sourcedocs.sealights.io/knowledgebase/settings/quality-gatesread 2026-11-20 |
|
| Triggers & Channel Coverage | Full |
|
Incoming code changes and test executions reach SeaLights through the delivery pipeline. The resulting decision can change which tests the runner executes for that build. Periodic runs of the entire suite can also be tied to the first build of the day or week, or to a count of test cycles. New and pinned tests can remain in the selected group even when a change does not directly affect them. Sourceshiftsync.tricentis.com/sealights-79/mission-impossible-how-to-increase-development-velocity-while-maintaining-quality-with-test-impact-analysis-1640read 2026-11-20 |
|
| Model Flexibility & Routing | Not documented |
|
Test Impact Analysis uses machine learning to identify which existing tests exercise changes in an application. It also incorporates known failures and tests the team has pinned or has yet to run. The release team can tune when it runs the whole suite and how it sets coverage thresholds, while model selection remains part of the managed analysis service. Sourceshiftsync.tricentis.com/sealights-79/mission-impossible-how-to-increase-development-velocity-while-maintaining-quality-with-test-impact-analysis-1640read 2026-11-20 |
|
| APIs / SDKs / MCP Extensibility | Full |
|
The SeaLights REST API accepts tokens from the customer's dashboard and exposes analytics, coverage and test optimization resources. Application quality gate settings can be managed through the API. The MCP server can run locally through Docker or a command line process and uses separate API or agent credentials to connect to a SeaLights domain. Client tools can query the account without using the dashboard. Sourcepostman.com/tricentis-sealights/sealights/collection/qeyeub5/sealights-public-apiread 2026-11-20 |
|
| Testing, Debugging & Optimization | Full |
|
Quality Gates evaluate changed code coverage, total coverage and optional failure thresholds before a build moves forward. The coverage calculations can target selected test stages and the failure count can represent all executions or the latest result for each test. Test Impact Analysis also changes the test workload for the next build, while periodic full runs preserve broader checks. Sourcedocs.sealights.io/knowledgebase/settings/quality-gatesread 2026-11-20 |
|
| Browser / Computer-use | Not documented |
|
The SeaLights browser extension displays metrics in source control and can report tests that a person performs manually. The extension uses the user's group permissions to decide which applications it exposes. Code scanners and listeners collect coverage for other executions, while test tools such as Testim supply interaction with the application itself. Sourcedocs.sealights.io/knowledgebase/settings/token-access-and-managementread 2026-11-20 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Quote only
What is public
Tricentis sells SeaLights through a product specific demo and sales process. The product covers quality intelligence for custom applications and for SAP transports.
Billing mechanics
The commercial agreement covers the SeaLights tenant. A deployment also uses the customer's build and test infrastructure, with separate instrumentation and connections for the applications and test stages in scope.
Variable cost rationale
The product is sold by agreement. Deployment can span more applications, test stages and SAP systems, and the license and expansion terms depend on the proposal.
Sales call required
Yes, required for paid access
Commercial notes
Teams can adopt SeaLights with their existing build and test systems. A connection to Testim test optimization requires a paid Testim tier.
Missing data
Base license prices, capacity allowances and SAP package terms are quoted.
Related vendors
- AlertD — AI agents for AWS operations that run read only in the customer's…
- Anyshift — AI SRE built on a versioned knowledge graph of infrastructure, apps…
- Avesha — Obliq, Avesha's autonomous AI SRE for Kubernetes and agentic…
- AWS DevOps Agent — AWS DevOps Agent investigates incidents and proposes mitigations for…
- Better Stack — Better Stack offers incident management with built in on call,…
- BigPanda — BigPanda is an agentic IT operations platform whose Biggy agents…
Alternatives to SeaLights
Other products that do the work SeaLights does, and what each one is.
- Ciroos AIAI SRE for complex enterprise estates
- Resolve AIAI SRE
- AnyshiftAI SRE
- Better Stack
- BluebricksContext and control layer
- HarnessHuman aware change agent