greyboxed Start free trial

TestCube

Test management that reads the Jira story first.

TestCube is test case management for teams on Jira Cloud. It keeps your test cases, runs and CI results linked to the stories they cover, so testers and Claude agents work from the same plan and every result shows who recorded it.

Start free trial Try the run screen

15-day free trial, no card needed. Built for teams on Jira Cloud.

Run a test the way testers actually do: from the keyboard.

Record each result with one key and move to the next case. A failed step offers a Jira bug with the steps, environment and screenshots already filled in. Try it below.

Release 4.2 · Regression Staging · Chrome 130 · assigned to you
38 / 120
Hand off to Claude agent
TC-143CriticalManualResult: Untested

3-D Secure challenge succeeds

Preconditions: Test card 4000 0027 6000 3184 that always asks for 3-D Secure.

#ActionExpected result
1Pay with the 3-D Secure test cardBank challenge opens in a modal
2Approve the challengeModal closes without a page reload
3Wait for confirmationOrder is confirmed within 10 seconds

Keys P, F, B, S and N work while the run screen is on screen.

Requirements stay in Jira. Coverage shows up next to them.

Link cases to Jira issues and TestCube builds the requirements traceability Jira can't show on its own: which stories have tests, which are failing, and which have none yet. Filter by sprint, version or environment.

  • An issue panel in Jira shows linked cases, coverage and the latest run.
  • When a story changes, its linked cases are flagged as possibly outdated.
  • Export the matrix with its audit trail to XLSX or PDF.
RequirementCasesLatest resultsCoverage
SHOP-412 Saved cards at checkout6Failing
SHOP-405 3-D Secure 2 support9Failing
SHOP-417 UPI collect payments3Partial
SHOP-420 Refund to original method5Covered
SHOP-431 Guest checkout with OTP0No tests
6 stories have no test cases. Claude can draft cases from their acceptance criteria for review.

TestCube for Jira

A TestCube tab on each Jira project shows how every story in a release is tested, and each story shows its own coverage. Your stories stay in Jira.

The TestCube tab in a Jira project: totals for stories that pass, fail, aren't run or have no tests, and a list of stories with their test coverage.
The TestCube tab in a Jira project.
The TestCube section beside a Jira story: 7 cases, 1 failing, 1 outdated, with the linked test cases and their results.
Coverage beside every story.
The TestCube panel on a Jira story: a coverage bar, the linked test cases with their results, and buttons to generate test cases with Claude or link a case.
Link cases and draft new ones with Claude, without leaving Jira.

Screens show sample data.

Agents join the team as named members.

TestCube has a built-in MCP server. Claude Code, Claude Desktop and CI agents sign in as a real person on your team, get that person's role, and every change they make is logged as “Priya via Claude Code”.

  • Draft test cases from a story's acceptance criteria. Drafts always go through review.
  • Turn approved steps into a Playwright spec, linked back to the case.
  • Group CI failures by cause: real bug, flaky or environment.
  • Hand a manual run to an agent that tests through the browser and attaches screenshots. Low-confidence results go to a person. This one is in beta.
Which Sprint 42 stories still have no tests?
testcube · list_untested_requirements6 stories, including SHOP-431 Guest checkout with OTP
testcube · create_caseTC-212 “Guest pays after OTP verification” saved as a draft for review
Logged as Priya via Claude Code
Likely real bug

Currency label shows USD for India billing

4 tests

Assertion expects “₹” but the page renders “$”. This started in commit 7f3c2ad, which changed formatPrice(). Linked requirement: SHOP-398.

The rest of a test team's week

Reviewed cases
Cases move from draft to in review to approved, like a pull request, with full version history.
Reusable steps
Shared steps and parameter datasets, so one change updates every case that uses it.
CI results in one request
Reporters for Playwright, JUnit, pytest and Cypress. Tag a test with @TC-123 to link it to its case.
Plans and milestones
Group runs by release, environment and browser matrix. Assign cases and see who has too much on.
Bring your history
Import from CSV, Qase JSON, TestRail XML and Xray, including past runs.
Audit log
Every change by every person and agent, exportable. Webhooks are signed and retried.

One plan. Viewers are free.

Every workspace starts with a 15-day free trial, no card needed. After that:

$35per paid seat each month, billed monthly

  • ₹3,500 per paid seat each month in India.
  • Prices exclude sales tax, VAT and GST, which are added at checkout.
  • No seat minimum.
  • Free viewer seats, up to twice your paid seats.
  • 15-day trial, no card needed.
  • About $5 of Claude usage per seat each month, or bring your own Anthropic key.

Questions teams ask

Is TestCube free?

Every new workspace starts with a 15-day free trial, no card needed. After that, TestCube costs $35 per paid seat each month with no seat minimum, and viewer seats are free up to twice your paid seats. Small teams can ask for a free tier of 3 seats.

Does TestCube work with Jira Data Center or Jira Server?

No. TestCube works with Jira Cloud only. It installs as a Forge app with an issue panel, and your requirements stay as Jira issues. TestCube links to them rather than keeping a second backlog.

Which test automation frameworks can send results?

Playwright has a first-class reporter, and there are reporters for JUnit XML, pytest and Cypress, plus Allure-compatible results. Each CI run sends its results in one request. Tag a test with its case ID, such as @TC-123, to link the two.

How do Claude agents connect to TestCube?

Through TestCube's built-in MCP server. Claude Code and Claude Desktop sign in as a member of your team with OAuth, and CI agents use a workspace token. Agents get the same role checks as the person, and the audit log records each change as that person via the agent.

What do the AI features cost?

Each paid seat includes about $5 of Claude usage a month, shown in TestCube as credits. If your team needs more, add your own Anthropic API key and AI keeps working past the included credits.

Is TestCube an alternative to Xray or TestRail?

Yes. TestCube does both jobs in one product: test management (cases, plans, runs and reports) and requirements traceability against Jira Cloud issues. It imports Xray and TestRail data, including past runs, so you can move without losing history.

Can I move my tests from another tool?

Yes. TestCube imports CSV, Qase JSON, TestRail XML, and Xray and Squash formats, including past run history, so reports don't start from zero.

Where is my data stored?

TestCube runs on AWS in Ireland (eu-west-1). Attachments go straight to storage rather than through the app, and every workspace's data is kept separate at the database level.

Who makes TestCube?

Greyboxed, an independent software company in India. The name comes from grey-box testing: testing with partial knowledge of a system's internals, which is how TestCube's agents work.

Start your 15-day trial

Create a workspace, invite your team and connect Jira Cloud. Everything is included during the trial and no card is needed. Choose a plan when you're ready, or keep viewing and exporting your data if you don't.

Start free trial

Questions first? Email hello@greyboxed.dev.