FAQ
Answers to common questions about using BesTest for test management in Jira - install, pricing, data, features, and what's on the roadmap.
Quick answers to the questions we hear most. Can't find yours? The support portal is one click away.
Getting started
No. BesTest is a Jira app, not a separate tool. It installs into Jira Cloud from the Atlassian Marketplace and runs inside Jira - no extra login, no new interface to learn. It follows the Atlassian Design System, so it looks and feels like a native part of Jira. You'll find it in the global Apps menu and in the project menu bar at the top of each project.
Install it from the Atlassian Marketplace. The first time you open it from the Apps menu or a project's menu, press Allow access to grant the permissions it needs - and you're in. There are no setup scripts or provisioning steps. See Installation for details.
A project admin enables it in one click from the project settings sidebar, under the BesTest menu. Enabling (or disabling) BesTest for a project takes about a minute. See Enable BesTest for a project.
Follow the flow: create requirements, write test cases (step-by-step or BDD) and mark them active, link test cases to requirements to build coverage, optionally group them into collections, then run them in test cycles and track progress in the Dashboard and Reports. The Quick Concepts page walks through it end to end.
Pricing & plans
Yes - completely free for teams of up to 10 users, with every feature included. No feature gating, no trial countdown. See the pricing page for the full breakdown.
Tiered per-user pricing that gets cheaper as your team grows. It starts at $1.79/user/month for 11-100 users and drops with every tier, all the way down to $0.01/user/month for the largest organizations. Billing runs through the Atlassian Marketplace - monthly or annual, with annual saving roughly 17%.
Yes. Every Atlassian Marketplace app includes a free evaluation period, so you can trial BesTest with your whole team before you commit to a paid plan.
Everything. There are no premium-only features - requirements, test cases, test cycles, Smart Collections, reporting, Jira dashboard gadgets, integrated bug reporting and dark theme are in every plan. Your price depends only on your team size, not on which features you use.
Security & data
BesTest is built on Atlassian Forge and stores your test data in a dedicated, secure database with enterprise-grade architecture. You can host your data in the EU, US, or India, and any other region can be provisioned on request.
No. Your requirements, test cases and executions live in BesTest's own data store - not as Jira issues - so your test library never bloats Jira or slows it down. When you do want a Jira issue (for example, to log a bug found during execution), BesTest links to it directly.
Yes. Built on Atlassian Forge and following the Atlassian Design System, BesTest feels like part of Jira - the same look, the same navigation, and single sign-on with your existing Atlassian account. There's nothing separate for your team to log into.
Using BesTest
Coverage isn't just "this requirement has at least one test." BesTest calculates each requirement's significance from its development complexity and impact, then tells you whether it has enough coverage for how much it matters - so a critical requirement and a trivial one are never treated the same. See Requirements.
Yes. Test cases can be plain step-by-step or written in BDD (Gherkin) Given / When / Then format. See BDD (Gherkin).
Dynamic groups of test cases defined by rules (filters) instead of hand-picked lists - so a collection stays current as your library changes, and you can drop a whole collection into a test cycle to build it in seconds. See Test Collections.
Not directly - BesTest doesn't store attachments yet. When you need to capture evidence such as a screenshot of a failure, create or link a Jira issue from BesTest and attach the file there. That keeps your evidence with the work item it belongs to.
Yes. When a test doesn't pass, you can create or link a Jira work item (a bug) right from the Test Player, so your execution results stay connected to the Jira issues they produced.
Migration & integrations
Yes. BesTest imports test cases from CSV in batches - up to 10,000 rows or 10 MB per file - with built-in validation that catches common mistakes (like invalid field values or a non-existent owner) before anything is imported. You can export your data back out too. See Import, Export.
The MCP integration is in open beta - it lets testers, developers and test managers create, update and query their testing data (and build custom reports) in natural language through AI assistants like Claude. A REST API is on the roadmap, working from the same source of truth. See [BETA] MCP.
Yes. BesTest ships Jira dashboard gadgets, so you can surface coverage and execution metrics right on your existing Jira dashboards - next to everything else your team already tracks. See Jira Dashboard Gadgets.
Roadmap & help
Not yet - version history for requirements and test cases is on the roadmap. If it's important to your workflow, let us know on the feedback board so we can weigh it in.
A built-in requirements module with significance-weighted coverage, review workflows, Smart Collections and no Jira issue bloat - typically at a fraction of the price. See the full breakdowns: BesTest vs Xray and BesTest vs Zephyr Scale.
Reach the team through the support portal for questions and problems, and share feature ideas on the feedback board (use Give Feedback at the top).
Open a ticket in the support portal - we're happy to help you get set up.