The tests your PR is missing, drafted for you.
Test Writer finds the functions a pull request changed that no test covers, then drafts unit and integration tests in your framework and style. Developers review, edit and commit them like any other code.
How tests get drafted
Test Writer works from the diff and your existing test suite, so new tests look like the ones your team already writes.
Major frameworks
Jest, Vitest, PyTest, JUnit 5, Go test, RSpec, xUnit and NUnit, detected from your repo.
Changed code first
Effort goes where risk just went up, not into generating tests for stable code nobody touched.
Unit and integration
Pure function tests where possible, integration tests with your test database or HTTP client where needed.
Readable test names
Each test says what behavior it proves, so a failing test explains itself.
Works with your CI
Drafted tests run in GitHub Actions, GitLab CI, Jenkins or CircleCI before they are offered.
No flaky padding
Tests that depend on time, randomness or network without control are discarded, not suggested.
Common questions
No. It only drafts tests for changed code without coverage, and only offers tests that pass and assert something meaningful. You choose which ones to commit.
Yes. Test Writer detects the framework and conventions per package, so a Python service and a TypeScript app in the same repo each get tests in their own style.
Test Writer is part of the Team and Enterprise plans.
git merge feat/first-review into main
Review your
first repo free.
One repository, AI review on every pull request, no time limit. Connect it in about five minutes and the next PR gets a first pass in under a minute.