CLCoverLens
Sign inGet started

Runtime coverage · Test impact · Service maps

Know exactly what your tests really cover

CoverLens attaches lightweight agents to your running services and turns every functional test — automated or manual — into line-level coverage, attributed test by test, across every microservice it touches.

Start measuring See how it works
runtimes — Java, Node.js, .NET
3
runtimes — Java, Node.js, .NET
runtime overhead
<1%
runtime overhead
of tests attributed to code
100%
of tests attributed to code
run, however many shards
1
run, however many shards

Product

Coverage that answers questions, not just percentages

Agents for every runtime

Java (bytecode), Node.js (V8) and .NET (IL weaving) agents attach with one flag — no code changes, under 1% overhead. Parallel shards merge into a single run.

Per-test attribution

Every request carries its test's identity across service hops, so the platform knows which lines each Playwright, Cypress, Selenium or manual test actually executed.

Change-based test selection

Connect git, pick a date, and the diff is matched against what every test touched on its last run. Schedule only the impacted cases — minutes instead of hours.

Coverage campaigns

A regression that runs over days, mixing automation and manual testing? Start a campaign; every agent joins, resets and accumulates until you call it done.

A service map that is true

Built from recorded traces, not a diagram: which services requests walk through, in what order, and which methods run hottest.

Fits the tools you have

Playwright, Cypress, Selenium/JUnit 5, Postman, k6, GitHub Actions, Jenkins, GitLab CI, Kubernetes auto-attach — plus a plain REST API for everything else.

How it works

From first agent to change-based testing in an afternoon

  1. 01

    Attach the agents

    One JVM flag, one NODE_OPTIONS entry or one .NET startup hook per service — or a single Kubernetes annotation for the whole cluster.

  2. 02

    Run your tests

    Functional suites, UI automation, load tests, manual click-throughs. Each test names itself in a header; the agents do the rest.

  3. 03

    See what really ran

    Line-level coverage per service, per file and per test — with the gaps your suite never reaches called out explicitly.

  4. 04

    Run less, ship faster

    The next release only needs the tests its diff impacts. The platform picks them, schedules them and reports the verdicts.

Integrations

Plugs into the pipeline you already run

PlaywrightCypressSelenium / JUnit 5Postmank6GitHub ActionsJenkinsGitLab CIKubernetesJira / XrayTestRailZephyr Scale

Stop guessing what your regression suite covers

Attach the first agent in minutes. The first run tells you what your tests really reach — and what they never have.

Get started