SeaLights Technologies

SeaLights measures test gaps, specifically identifying methods and functions modified in a code change that went unexercised by any automated test. Unlike traditional code-coverage tools that report the percentage of lines hit during a test suite run, SeaLights correlates production-runtime telemetry with test-environment execution to flag which changes carry the highest regression risk. The output is a per-build quality score that release managers use as an automated gate. This metric is exposed via dashboards and API integrations with CI/CD pipeline tools like Jenkins and GitHub Actions.

Tricentis acquired SeaLights and now markets the capability as Tricentis SeaLights, a module within the Tricentis continuous-testing platform. The module ingests coverage data from Tricentis Tosca, the firm's model-based test-automation tool, alongside open-source test frameworks like JUnit and Cypress. Tricentis SeaLights applies the original SeaLights test-gap identification algorithms to that ingested data, producing quality-risk analytics for Tricentis' enterprise customer base. Integration is native, meaning no separate SeaLights licensing or deployment is required.

SeaLights historically supported Java, .NET, and JavaScript ecosystems, with instrumentation agents that attach at the bytecode or runtime level to collect coverage telemetry. Dependency and build-tool compatibility included Maven, Gradle, and npm. Test-framework integrations covered JUnit, TestNG, NUnit, MSTest, Jest, and Mocha among others. Post-acquisition, Tricentis aligned support with the Tricentis Tosca coverage map while maintaining compatibility with open-source framework ingestion.

SeaLights offered both SaaS and on-premises deployment options. The on-premises model was common among financial-services and insurance clients with strict data-residency requirements, since SeaLights' coverage instrumentation captures source-code and test-execution metadata that some security policies require to stay behind the corporate firewall. The architecture uses lightweight agents in build and test environments that stream data to a centralized analytics server, with optional proxy configurations for air-gapped networks.

Standard code coverage reports what percentage of lines, branches, or functions a test suite executes. A coverage figure of 85 percent can mask the fact that the remaining 15 percent includes a critical newly modified payment method that no test touched. SeaLights identifies exactly those methods by comparing instrumentation data between test and production environments, isolating code paths that changed but were never exercised. This shifts the lens from overall coverage magnitude to change-specific quality risk, letting teams tolerate lower line-coverage percentages while raising flags only on untested modifications.