Requirement & Test management for Jira.
AI agents coming soon.
The source of truth linking requirements, test cases, coverage, and results - readable and writable by your team, your CI pipeline, and your coding agent.
| Key | Name | Status | Test status |
|---|---|---|---|
| REQ-142 | Password reset by email | Covered | 51 |
| REQ-143 | MFA enrolment | Ready | 32 |
| REQ-150 | Checkout flow | Covered | 8 |
| REQ-161 | Webhook retry & backoff | Draft | 14 |
| REQ-170 | Session timeout | Ready | 21 |
Password reset by email
- TC-318Reset link expires after 24hPassed
- TC-320Rate limit after 5 attemptsFailed
Xray
Zephyr Scale
TestRail
AIO Tests
RTMOne source of truth.
Three ways to work.
A complete set of test-management tools your team uses by hand today - built so the same requirements, tests, and coverage can be driven by your CI pipeline and your AI agents next.
Manual & UAT testing
Create requirements and test cases, link them for coverage, and run manual or user-acceptance cycles step by step - then report and audit. All by hand, inside Jira.
- Manual & UAT cycles with business stakeholders
- Requirements ↔ tests ↔ executions linked
- Reviews, reporting and audit trail
Test automation
Connect your CI. Push results from your pipeline into the same coverage picture, and pull test data out through the REST API - manual and automated in one view.
- Full REST API for tests, runs & results
- Results flow in from every pipeline run
- Manual & automated, one coverage picture
Playwright
Cypress
Selenium
GitHub Actions
GitLab CI
Jenkins
PostmanAI-supported testing
Your agent talks to the foundation over MCP: it reads requirements and coverage, generates automated tests, catches and re-runs flaky ones, and syncs results back.
- MCP server - bring any AI agent
- Requirements-aware test generation
- Detect, regenerate & re-run flaky tests
- Scoped to your permissions · code stays in your repo
Claude
OpenAI Codex
Cursor
GitHub Copilot
Gemini
Windsurf
Atlassian RovoWhat your team gets.
The surfaces below mirror the BesTest UI, rendered live on this page - the dashboards are the app's actual components, the rest are faithful recreations of what you get after install. Scroll through all 6 core screens, or jump to any of them.
BesTest lives inside your Jira work item.
No separate tool to learn. Open any work item and the BesTest panel sits right inside it - every requirement, test case, cycle and execution linked to it, plus how to switch it on.
Apply a promo code at the payment step
BesTestBesTest- 1Switch it on onceOpen the Apps (...) menu on any work item and pick BesTest. The panel pins to the bottom of the work item - for the whole team.
- 2Your section, in the work itemIt sits between Child issues and Activity - the full work item, not the side panel. Familiar Jira around it; this part is ours.
- 3Every linked object, liveRequirements, test cases, cycles and executions for this work item, each with real status and recent runs.
- 4Create or link in placeSpin up a requirement or test case inline, or Link existing ones - without leaving Jira.
Your whole test library, organized.
Folders on the left, your items in the middle - the same catalog for requirements, test cases, cycles, collections and campaigns. This is how everything is stored.
folder = "Authentication" AND (priority in (High, Highest) OR label ~ "regression")Apply12 resultsClear| Key | Name | Status | Priority | Owner | Updated | |
|---|---|---|---|---|---|---|
| TC-318 | Reset link expires after 24 hours | Active | High | MM. Lee | 2d ago | |
| TC-319 | Invalid email shows inline error | Active | Medium | MM. Lee | 3d ago | |
| TC-320 | Rate limit after 5 failed attempts | Changes Needed | High | DDana K. | 1d ago | |
| TC-150 | Session times out after idle period | Active | Medium | DDana K. | 5d ago | |
| TC-091 | Password complexity is enforced | In Review | Low | AA. Roy | 1w ago | |
| TC-204 | Remember-me persists for 30 days | Draft | Low | TT. Wong | 2w ago | |
| TC-377 | Account locks after repeated failures | Active | Critical | DDana K. | 4d ago | |
| TC-143 | MFA enrolment sends SMS code | Active | High | AA. Roy | 6d ago | |
| TC-161 | Reset token is single-use | In Review | High | PP. Costa | 3d ago | |
| TC-188 | Expired link shows resend option | Active | Medium | MM. Lee | 1w ago | |
| TC-205 | Reset disabled for SSO accounts | Archived | Low | SS. Varga | 1mo ago |
- 1Folder treeNested folders per project. Every object type - requirements, test cases, cycles, collections, campaigns - has its own catalog.
- 2BQL - query your tests like JQLHit Filter and write real queries - folders, fields and labels composed with AND/OR - or build the same rule visually. Built to scale to thousands of cases.
- 3Live statusesAtlassian-style lozenges show review and execution state at a glance.
- 4Act on many at onceSelect any cases and the floating bar appears - add them to a cycle, move folders, or archive your whole selection in one go.
Five objects. Each one first-class.
Open any item and the full viewer opens. The tabs change per object: requirements have Coverage, cycles have an Execution Dashboard, collections have Rules. Switch between them.
Rate limit after 5 failed attempts
After five consecutive failed sign-in attempts the account is temporarily locked and the user is shown a clear recovery path.
- Priority
- High
- Type
- Security
- Automation
- Manual
- Folder
- Authentication
Run every test, step by step.
The manual test player: pick a result for each step, capture evidence, and raise a linked Jira defect without leaving the run. This is UAT and manual testing, done inside Jira.
- 1Live cycle stats and timerExecution progress, the running timer and per-status counts stay pinned in the header while you work the cycle.
- 2Shape the list your wayGroup the run by folder, status or assignee, collapse what you are not running, and jump to any case - the list bends to how your team works.
- 3Result per stepPass, fail, block - or raise a Jira bug - right on the step, with the actual result recorded inline. Try it.
Release-readiness on your Jira dashboard.
Twenty configurable gadgets - coverage, execution status, trends, active cycles - right where your team already looks. Management gets the answer to "are we ready to release?"
Prove coverage, end to end.
The Requirements Traceability report - the one auditors and managers ask for: every requirement mapped to its test cases, colored by the latest run, with the defect trail attached. It is one of five purpose-built reports, each hand-tailored to a real release question, and exports the moment the audit asks.
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
ClaudeOpenAI CodexCursorGitHub CopilotGeminiWindsurfAtlassian Rovo✓ reset link expires after 24h
Smart Collections build your cycles for you.
Gather test cases three ways - then turn the collection into a cycle in one click, and it stays current as your library grows.
- 1Pick them by handA fixed list of test cases you choose - simple and explicit.
- 2Define a ruleDynamic membership from folders, fields and labels - composed with AND/OR, as deep as you need.
- 3Point at requirementsSelect requirements and the collection resolves their coverage when you use it - always the current set.
Teams switch and stay.
“We've tried a lot of test tools over the years, but none really fit how our team works with test sessions. BesTest let us set up tests and run them with full traceability, nested folders, and issue links for any found issues. It fits our workflow really well.”
“Setup took like 5 minutes and there's basically no learning curve. Everything included - requirements, test cases, executions, reports. It just works. The folder/collection organization is intuitive and the built-in review workflow for test cases is handy. Feels like it was actually made by testers who get it.”
More built in. A fraction of the price.
| BesTest | Zephyr | Xray | AIO Tests | RTM | |
|---|---|---|---|---|---|
| Built-in requirements module | |||||
| No Jira issue bloat (separate DB) | |||||
| Built on Atlassian Forge | partial | partial | partial | ||
| Test case review workflow | partial | partial | |||
| Smart Collections (auto cycles) | |||||
| Release prediction | partial | partial | |||
| REST API & automation | soon | ||||
| Free tier (all features) | |||||
| Price / user at 100 users | $1.79 | $6.81 | $6.33 | $1.98 | $1.91 |
REST API, CI/CD and automation arrive summer 2026. We are honest about the roadmap. Competitor prices per user at 100 users, as of June 2026.
Every feature, every tier.
No feature gating. Free up to 10 users - while Xray and Zephyr charge from your very first user - and 3-4x cheaper than either at scale.
- Requirements + test cases
- Smart Collections & reviews
- Reporting & dashboards
Live in about a minute.
- ~30 seconds1.Install from the Marketplace
One click on "Get it now" - no sales call, no signup form, no separate login.
- ~1 minute2.Enable it on a project
Flip it on in project settings. BesTest shows up in the project menu, where your team already works.
- right away3.Run your first test
Create a requirement, link a test case, hit run. No training course required.
Learn the craft.
Questions, answered.
Is BesTest really free?+
Yes - free for up to 10 users with every feature included. Paid tiers start at $1.79/user/month and scale down at volume.
Does it work with my Jira?+
BesTest installs from the Atlassian Marketplace as a Jira app built on Forge. No separate login, no new interface - it follows the Atlassian Design System.
Where is my data hosted?+
BesTest supports regional hosting in the EU, US, and India, and keeps your test library from cluttering Jira issues so Jira stays fast.
When do the REST API and AI agents arrive?+
This summer. Manual and UAT testing is live today; the REST API and the MCP integration for AI agents are coming next, on the same source of truth.
How is it different from Xray or Zephyr?+
A built-in requirements module with significance-weighted coverage, built-in review workflows, Smart Collections, and no Jira issue bloat - at a fraction of the price.
Bring requirements and tests together in Jira.
Free for up to 10 users, every feature included. One click from the Atlassian Marketplace, about a minute to enable on a project.