Test data is valuable only when the right people can access it. With Snapshots for TestRail, teams can bring TestRail data into Confluence alongside Jira information, giving stakeholders a shared view of test coverage, traceability, and results without requiring every reviewer to work directly in TestRail.
The challenge
TestRail gives QA teams a central place to manage testing, but product managers, engineering leaders, auditors, and other stakeholders often work in different systems. When they need visibility into test coverage, release readiness, or traceability, QA teams may have to export spreadsheets, generate PDFs, or switch between tools to share the right information.
In regulated environments, this process becomes even more complex. Release documentation and traceability reports often need to reflect the exact state of testing at a specific point in time, which can make manual reporting time-consuming and error-prone.
The solution
Snapshots bridges the gap between testing, requirements, and documentation by bringing TestRail and Jira data together inside Confluence.
Teams can create configurable snapshots that combine requirements, test cases, test runs, and results in one view. Because Snapshots preserve historical versions, teams can track changes over time and provide documentation for audits, releases, and stakeholder reviews.
About the integration
The TestRail integration extends Snapshots for Jira Data into Confluence, allowing teams to incorporate TestRail data directly into Confluence pages.
With Snapshots, you can build Confluence pages that display TestRail data directly: Test Cases, Test Runs, Results, or Test Plans. These can stand alone or be combined with Jira issues in a hierarchical view, creating traceability reports that connect requirements to tests and outcomes. This linking uses TestRail’s References and Defects fields, so teams can see what was tested and how it performed.
Each snapshot is fully configurable, with support for standard and custom TestRail fields. And because every snapshot is versioned, teams can compare changes between releases and preserve historical records for audits or future reference.
Benefits of using Snapshots with TestRail
- Share test visibility without additional licenses: Managers, auditors, and stakeholders can review TestRail coverage, traceability, and results directly in Confluence—without requiring their own TestRail licenses.
- Connect requirements and testing: View Jira issues, TestRail test cases, test runs, and results together for clearer traceability.
- Simplify release documentation: Replace manual spreadsheets and exported reports with versioned snapshots stored in Confluence.
- Capture point-in-time evidence: Preserve historical snapshots to compare releases and support audit preparation.
- Customize reports: Choose the fields, filters, and hierarchy that fit your process, including custom TestRail and Jira fields.
How the integration works
Getting started is straightforward.
At a glance:
- Install Snapshots for Jira Data and the TestRail extension.
- Connect your TestRail Cloud instance using an API key.
- Add a Snapshots macro to a Confluence page.
- Select TestRail data, configure fields and filters, and generate a combined TestRail + Jira view.
- Refresh snapshots as needed while preserving historical versions for traceability and audits.
Start by installing Snapshots of Jira Data into Confluence and the TestRail extension from the Atlassian Marketplace. Connect your TestRail Cloud instance using an API key.
Then add a Snapshots macro to any Confluence page. Choose your root entity (Jira issues, Test Plans, Test Runs, or Test Cases) and build a hierarchy beneath it. For example, start with Jira stories and nest their linked test cases and results underneath. Configure filters and select which fields to display. The result is a single table combining TestRail and Jira data, right on the page.
Refresh anytime to capture the latest state. Previous versions are preserved, so you can compare snapshots over time and see exactly what changed between releases.
For detailed setup instructions and configuration options, refer to the Snapshots documentation.
Bottom line
As Rina Nir, CEO and Co-founder of RadBee, puts it:
“We’ve learned that when test data stops being siloed, everything changes. Release documentation gets easier. Cross-discipline collaboration starts to work. We’ve seen it happen, and we’re thrilled to bring that same capability to TestRail users.”
Testing data shouldn’t live in isolation.
Snapshots for TestRail brings test coverage, results, and traceability into Confluence, where teams already collaborate and document their work. By combining TestRail and Jira data in versioned snapshots, organizations can eliminate manual reporting, simplify audits, and provide stakeholders with a shared view of release quality—all without adding more tools or licenses.
Whether you’re preparing for a release, generating compliance evidence, or simply improving visibility across teams, Snapshots helps turn testing information into a resource the entire organization can use.
About TestRail
TestRail is the only centralized QA platform that gives you the power to build, connect, and optimize all of your testing processes. Over 10,000 QA teams use TestRail to release flawless products faster by testing more efficiently, getting real-time visibility at scale, and building confidence in QA.
About RadBee
RadBee is an Atlassian Marketplace partner focused on helping teams bridge the gap between test management and documentation. Their Snapshots app is used by companies in pharma, medtech, life sciences, banking, and automotive. It brings Jira and test data into Confluence without extra licenses, improving cross-discipline collaboration.
