Product · Tests

The tests your team never gets to.

Cortex writes the tests. Open a PR and Cortex generates the unit and integration tests that should ship with it — matching your framework, your patterns, and your coverage goals. Backfill old code on demand.

PR opened#4291

feat: refund partial orders

Tests written6 cases

happy path · edges · auth · error states

Coverage +4.2%passing

refunds.ts now at 92% lines

How it works

Coverage that writes itself.

Cortex slots into your existing test framework — Vitest, Jest, Pytest, Go test, RSpec — and authors the cases your team would write if there were time.

01

Point at a file or PR

Pick a function, a module, or an open pull request. Cortex reads the surrounding code and conventions.

02

Cortex drafts the cases

Happy paths, edge cases, error states, and auth boundaries — written in your framework's style.

03

Review the test plan

See every case before any code is written. Reject ones you don't want, refine the rest in plain English.

04

Tests land in a PR

A draft PR adds the new tests to your repo. Your CI runs them. You review and merge.

Features

Tests that look like your team wrote them.

Framework-native

Vitest, Jest, Pytest, Go test, RSpec, and more — Cortex writes in the style your repo already uses.

Convention-aware

Existing helpers, fixtures, and mocks get reused. New tests look like neighbours, not strangers.

PR-aware coverage

Open a PR and Cortex covers exactly what changed — the new function, the new branch, the new edge case.

Backfill old code

Point Cortex at an untested module and it'll author a full test plan, then ship the cases as a PR.

Plans before patches

Every test run starts with a reviewable plan. You approve which cases get written before any code lands.

Strict org isolation

Your code, embeddings, and tokens stay scoped to your organization with row-level security.

Stop skipping tests. Start shipping coverage.