What is ATM

Test management is how a team plans, writes, runs, and tracks its tests. Appsvio Test Management (ATM) is a test management app for Jira. ATM is available only for Jira Cloud. It’s an alternative to Xray and Zephyr.

ATM is built on Atlassian Forge. All ATM data, including attachments, stays on the Atlassian side.

What test management is for

Test management answers what to test, how to test it, and what the results are. In ATM, each of these has its own testing object:

• A Requirement says what needs to be tested. Any work item can be a requirement, for example an Epic, a Story, or a Task.
• A Test Case says how to test it, with test steps and preconditions.
• A Test Plan sets the scope of testing. You can run it many times, for example on different environments.
• A Test Campaign groups one or more Test Plans, so the business can track testing progress.
• A Test Execution groups the Test Cases you run together. Running a single Test Case creates a Test Case Execution, where testers record its result, per step and as a whole.
• While you run a test, you create a Defect from a test step or from the whole Test Case Execution. The Defect is linked to that Test Case Execution.

For all seven objects and how they connect, see Testing objects & Relations.

Why do test management in Jira

ATM brings testing into the same tool as the rest of your work, whether you test software, business processes, or system rollouts. Requirements and defects usually already live in Jira, and your tests join them there.

Instead of keeping Test Cases in Excel, you keep them as Jira work items that you can track.

• The testing process in ATM uses five dedicated types of objects: Test Cases, Test Plans, Test Campaigns, Test Executions, and Test Case Executions. ATM creates them automatically when you create the sample project.
• All testing objects except Test Case Executions are Jira work items. Test Case Executions are ATM’s own objects.
• You search for testing objects with JQL. You can show selected Test Cases on dashboard gadgets.
• You add any information to testing objects with custom fields. You can use Jira workflows, for example to approve Test Cases or Test Plans.
• ATM supports both company-managed and team-managed spaces.
• On the Atlassian Marketplace, ATM has the Atlassian Enterprise Certified and Runs on Atlassian trust signals and the Partner supported label.

To see what ATM adds to Jira and what you can customize, see ATM in Jira.

Built for regulated industries

ATM is a good fit for regulated industries: banking and finance, insurance, healthcare and pharma, medical devices, automotive, the public sector, aviation and space, and energy.

• Your test data stays in Atlassian infrastructure. ATM runs fully on Forge, with no data egress and with data residency in 12 Atlassian regions.
• ATM supports Atlassian Isolated Cloud since October 1, 2026.
• An audit in a regulated industry asks for proof that every requirement was tested. ATM gives you traceability from requirements through Test Cases to defects, the Coverage Report, and test steps versioning included in every plan.

ATM helps you collect the testing evidence that regulations and industry standards require.

How to get started

After you install ATM, go to Quick Start and create the sample project. It’s the easiest and fastest way to evaluate ATM.

What’s included in this doc

• About ATM: the architecture, support for Atlassian Isolated Cloud and Atlassian Government Cloud, editions, and pricing.
• Getting Started: installation, testing objects, navigation, and the Quick Start.
• Defining Requirements: requirements and their coverage with Test Cases.
• Writing Tests: Test Cases, test steps, preconditions, steps versioning, and Test Cases created with the Rovo agent.
• Organizing Tests: Jira Space, the Test Repository, and Jira fields.
• Planning Tests: Test Plans and Test Campaigns.
• Executing Tests: Test Executions, how to create and run them, test steps execution, defects, and retests.
• Import & Export: import, export, and migration from Xray.
• Reporting: reports, including the Coverage Report and the Traceability Report, and the Testing Project Dashboard.
• Administration & Configuration: Testing Elements of a Testing Project, test step fields, environments, permissions, and ATM in Jira.
• Security: data residency and no data egress.
• Resources: a glossary of testing terms.

Customer stories

See how nBora works with ATM in the nBora success story.