Probe

expect(true).toBe(true) passes every time. Probe finds the tests that were written to satisfy CI rather than catch bugs.

What it catches

Tests that aren't really tests

Fake assertions

Patterns like expect(true).toBe(true), expect(x).toBeDefined() with no value check, or hardcoded expected values that can never fail.

Deleted coverage

Tests removed or commented out during refactoring. If the agent deleted a test file, you'll see it flagged with the coverage it previously covered.

Hardcoded secrets

API keys, passwords, and tokens found in new test files or fixture data that the agent created during the session.

Missing edge cases

Functions with error paths, null inputs, or auth guards — with no corresponding test for those branches.

How it works

Three checks per test

1

Collect the new tests

We gather every test file the agent added or changed this session — nothing else gets scored.

2

Inspect each assertion

Every assertion is checked: does it verify a real value, or just that something exists or is truthy?

3

Map the gaps

Deleted tests and untested branches are cross-referenced against the code that actually changed.

Example output

Probe

Fake assertion

expect(result).toBeDefined()

auth.test.ts:47 — passes regardless of result value

Deleted test

auth.integration.test.ts — removed

Covered: login flow, token refresh, session expiry