← Back to Products

TestPlan

Test management organised by feature.

Test cases hang off the features in your product, so you can see which features have tests, which runs passed, and what nobody has checked yet before a release goes out.

TestPlan dashboard

How it works

  1. Code changes land in an inbox. You flag the ones that need testing.
  2. Write test cases against the feature they belong to. Claude Code or another agent can draft them from the codebase through the MCP server.
  3. Run them. Each test is marked pass, fail or blocked as you go, with notes and screenshots.
  4. Release, with a record of exactly what was tested and what wasn't.
TestPlan - feature coverage dashboard

Tests by feature

Tests are organised by feature rather than by folder. Each feature shows how much of it is covered, so a gap is visible before a customer finds it.

  • Create features with descriptions and categories
  • Link test cases directly to features
  • View coverage percentages per feature
  • Track feature status: Active, In Development, Deprecated
TestPlan - live test execution

Test runs

Create a run, assign it to someone, and the results come in as they work through it: pass, fail or blocked, with notes, screenshots and how long each test took against the estimate.

  • Real-time pass/fail/blocked status
  • Notes and screenshots per test
  • Estimated vs actual time tracking
  • Feature-based grouping in the sidebar
TestPlan - change inbox

Releases

A release moves from draft to testing to released. It shows its coverage, the issues found before and after it went out, and a history of every change with the before and after values.

  • Draft, testing and released stages
  • Coverage tracking per release
  • Pre and post-release issue management
  • Complete audit history with before/after values

Exploratory session

Charter: try to break checkout with an expired card

42 minutes, 2 findings, both linked to Payments

Exploratory testing

Some testing is just poking at the thing to see what breaks. Start a session, write down what you are trying to break, and note findings as you go. The time is tracked and each finding is linked to the feature it belongs to.

  • Session-based ad-hoc testing
  • Charter goals to keep sessions focused
  • Automatic time tracking
  • Bug capture linked to features

$ claude

> "Create test cases for the login feature based on the codebase"

Using TestPlan MCP tools... 6 test cases created and linked to Login feature.

Claude Code and other agents, through MCP

TestPlan has an MCP server with 80+ tools. Connect Claude Code, GitHub Copilot or Cursor and it can read the features, write test cases from the codebase and record results, using your own AI subscription rather than one I charge you for.

  • 80+ MCP tools for full test management
  • Works with Claude Code, Copilot, and Cursor
  • Bootstrap full test suites from codebases
  • No proprietary AI or token charges

Setting up

  1. List the features in your product, grouped by area.
  2. Write test cases with steps and expected results, or have an agent draft them.
  3. Run them and record what happened.

It is free to start and there is no card to enter. test-plan.io

Ready To Get To Work?

I'm ready to get stuck in whenever you are...it all starts with an email

...oh, and tea!

paul@thecodeguy.co.uk