CodeVet

Turns dev tickets into reviewed test cases

Getting test cases your reviewers actually accept is a different problem than generating them. CodeVet builds context from your Jira project, your user documentation, and your existing test suite, then proposes test cases your team reviews and pushes into Xray.

112 vs 49

test cases per month, same team, same ticket flow

80%

of proposed test cases approved, across 640 review decisions

2 teams

using it independently, in daily production use

Measured directly in the product with our design partner, an enterprise video technology company, across two product teams.

How it works

Dev ticket Test briefing Your review Your test suite
01

Builds context

Builds context from your Jira project, user documentation, and existing test suite, so it understands your product.

02

Generates a test briefing

Generates a test briefing for any dev ticket you select, proposing test cases with steps and expected results.

03

Your reviewers accept or reject

Your reviewers accept or reject. Accepted tests are pushed into your test management system, where your team owns and edits them from that point on.

04

When ticket scope changes

The briefing updates to match, so your tests do not drift from what is being built.

Any AI assistant can turn a ticket into generic test cases

Getting them accepted takes knowing your product, not just the ticket in front of it: what your suite already covers, what changed last sprint, and where the risk actually sits. Then keeping those tests current as scope moves, and landing them in the system your team already works in.

Get that right and coverage keeps pace with what you ship, instead of slipping every time a release gets close.

Who this is for

01

Uses Jira

Uses Jira for dev tickets, with a test management system your team works in.

02

Someone owns test cases

Someone owns test cases and reviews them before they land: QA, an outsourced partner, or a tech lead.

03

Has at least one product

Has at least one product under active development, where requirements change and the suite has to keep pace.

Xray is supported today; your tool choice shapes what we build next. Not a fit without a review step.

Security first

Source code access is not required. Everything runs on AWS, with each customer in a dedicated tenant. Your tickets, documentation, and test cases are never used to train models.

Learn more about security

Pricing

Plans start at $1,250 per month, billed annually. Monthly billing is available.

Priced on the number of active projects and briefings generated. Unlimited users on every plan, no per-seat fee. One-time onboarding of $1,500 per project, run by a founder.

If it is not a fit, cancel in your first 30 days and we refund your subscription and your first project’s onboarding.

Larger teams needing an MSA, security review, a dedicated Slack channel, and a support SLA are handled as Enterprise agreements.

Request the full pricing sheet

Tell us about your setup and we will email the pricing sheet — no call required.

We use your details only to send the pricing sheet — see the Privacy Policy.

See CodeVet in action

Book a 30-minute call and see real briefings and generated test cases on a live project, not slides. If it fits, a founder runs your setup: connect Jira, your test management tool, and your docs, and your first project usually runs in a day or two. Every test you accept is yours, in your own system. No lock-in, by design.