BesTest Logo
BesTestTest Management for Jira
Now in beta

AI-Supported Testing,
Grounded in Your Requirements.

Connect your coding agent to BesTest over MCP. It reads your requirements and coverage, generates automated tests in Playwright or any language, and syncs results back - while your code stays in your own repo.

Get BesTest FreeSee test automation

Now in closed beta, access granted per user. Request access →

Agent-nativeNow in beta

Your coding agent becomes a tester.

The MCP server gives Claude Code, Cursor or Copilot direct access to the same source of truth your team uses by hand: it reads requirements and coverage, writes the missing tests in your repo, runs them, and reports results back into BesTest.

  • Requirements-aware test generation - the agent knows what to cover and why
  • Detects, regenerates and re-runs flaky tests
  • Results land in the same coverage picture as your manual runs
  • Scoped to your permissions · code stays in your repo
Works withClaudeClaudeOpenAI CodexOpenAI CodexCursorCursorGitHub CopilotGitHub CopilotGeminiGeminiWindsurfWindsurfAtlassian RovoAtlassian Rovo
claude · connected to bestest-mcp
$ claude "REQ-142 lost coverage last night - fix it"
⏺ bestest · get_requirement REQ-142
"User can reset their password by email" · significance: High
⏺ bestest · get_coverage REQ-142
82% covered · gap: rate-limit path (TC-320 failing)
⏺ Writing tests/auth/password-reset.spec.ts · 2 new Playwright tests
✓ returns 429 after 5 attempts
✓ reset link expires after 24h
⏺ bestest · push_results → cycle "Nightly API checks"
TC-320 Passed · REQ-142 coverage 82% → 100% · Covered ✓
your agent + BesTest over MCP
You: "Read REQ-204 (checkout flow) and its acceptance criteria
      from BesTest, generate Playwright tests for the paths that
      aren't covered yet, then create them as test cases linked
      to REQ-204."

Agent: reads the requirement and current coverage over MCP, writes
       the specs in your repo, and creates the linked test cases in
       BesTest - all scoped to your Jira permissions.

Illustrative - MCP server is in beta.

Now in beta

Now Supporting Your AI Agents
Requirements-Aware Test Automation

BesTest already links your requirements, test cases, and execution. Now your CI pipelines and coding agents can read and update all of it through our REST API and MCP server, with your testing context as the source of truth.

01

Connect

Add a development key in your BesTest project settings. Your IDE agent connects over our MCP server, scoped to exactly the Jira permissions you already have. Agents only ever see what you are allowed to see.

02

Understand

Agents pull requirements, test cases, test cycles, and coverage to understand what actually needs testing, grounded in your real project context instead of guesswork.

03

Act

Generate Playwright and automated test cases from requirement context, then push execution results back from CI through the REST API. Manual and automated land in one coverage picture.

MCP ServerREST APICI/CD pipelinesPermission-aware
On the roadmap

A deeper connection to Atlassian's Teamwork Graph and Rovo, so your agents reason over testing context alongside the rest of your organization's work, with permissions intact.

Get it Free on Marketplace

Now in closed beta, access granted per user. Request access →

What would you do with it?

Just ask. Your agent does the rest.

Because the MCP server exposes your requirements, tests and coverage, you talk to your test data in plain language. Real things teams ask on day one:

You

Which High-significance requirements lost coverage this week?

The agent reads coverage over MCP and hands you the list, with the tests that failed or went missing.

You

Read REQ-204 and generate Playwright tests for the paths that aren't covered, then create them as linked test cases.

New specs land in your repo; the matching test cases are created in BesTest, linked back to REQ-204.

You

Turn REQ-142's acceptance criteria into a test case with steps.

A step-by-step test case, drafted straight from the requirement, ready for a human to review.

You

Create test cases for every requirement in EPIC-12 that has none.

The agent finds the gaps and fills them in bulk, so nothing ships untested.

You

Are we ready to release sprint 14? What's uncovered or failing?

A readiness read-out: covered versus uncovered requirements and every open failure.

You

Summarize the executions from cycle KAN-CY-38 in a table.

A clean table of results on demand, without opening a single report screen.

Read the MCP guidePrefer code? See the REST API

Works with your agent

Built on the Model Context Protocol, so it connects to Claude Code, Cursor, and any MCP-compatible client.

Getting started

Live in about a minute.

  1. ~30 seconds
    1.Install from the Marketplace

    One click on "Get it now" - no sales call, no signup form, no separate login.

  2. ~1 minute
    2.Enable it on a project

    Flip it on in project settings. BesTest shows up in the project menu, where your team already works.

  3. right away
    3.Run your first test

    Create a requirement, link a test case, hit run. No training course required.

Host your data in the EU, US, or IndiaNo Jira issue bloat - your library stays out of Jira’s wayBuilt on Atlassian Forge

Ready to Get Complete
Testing Visibility?

Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!

Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.

Start Free on Marketplace

Enterprise Security

Built on Atlassian Forge.

Secure by design.

Built by Testers

Designed by QA professionals.

Updated every 2 weeks.

Free to Start

Get started for free and scale as you grow