More than test management.
Nexus connects the quality engineering workflow from requirement and test design through execution, environments, release readiness and sign-off.
Get started →- Requirements
- Test design
- Test execution
- Connected evidence
- Human review
For QA and release leads
Quality engineering in Jira, from requirement to sign-off.
Nexus connects requirements, test design, governed data, manual and automated execution, defects, environments and release decisions. Your team can follow what was tested, which inputs were used and whether the evidence still applies.
Know which evidence is current
A passing result belongs to a build and an environment. Record deployments and invalidating events, identify stale results, and plan re-runs. Readiness gates and recorded sign-offs keep the decision connected to the evidence available at the time.
Controlled test data
Keep repeatable inputs beside the tests: published versions, environment restrictions, classification and usage history. Follow a failed iteration back to the data it used instead of reconstructing the contents of a shared spreadsheet.
Manual and automated evidence together
Start a connected cloud pipeline from a cycle with Run in CI, or queue Run automation for the customer-hosted Nexus runner. Tests run in your infrastructure and results return to the same cycle.
Built from the work of quality assurance.
Resync is an independent New Zealand software testing and quality engineering consultancy. Resync Labs is its development arm, turning recurring delivery problems into products. Nexus applies that focus to testing inside Jira Cloud.
The product brings attention to the questions that shape a release review: what changed, what was tested, which inputs were used and what still needs attention. Nexus adds AI suggestions without removing the human decision: findings and generated tests remain reviewable drafts.
Check the fit for your team.
- Jira Cloud. Nexus is built on Atlassian Forge for Jira Cloud; it is not a Jira Data Center app.
- Your execution infrastructure. Automated tests run outside Jira, in your CI or on a machine running the customer-hosted Nexus runner. Nexus receives the resulting test report.
- Separate AI costs. Your AI provider bills your organisation separately for model usage. Your administrator connects the provider account, and its terms apply.
- Migration scope. Check the supported import formats before planning a move.
Check capabilities and release status · Plan with guides and checklists
Maintain the tests behind the release evidence.
Test ownership makes responsibility visible. Test debt helps identify library maintenance work, and the advisory Test health score describes the tests separately from the requirement Quality Score. Failure categories support triage, while regression-set suggestions help choose the next useful tests.
Your team reviews these signals and confirms the action. Suggestions do not silently change a cycle's scope or approve a release. Availability follows the site's enabled capabilities and Jira permissions.
Use the evidence beyond a single screen.
Release forecast and the Quality Executive Summary bring progress and risks into the release discussion. Scoped Nexus API access connects cases, plans, runs and other test records to your own tools, with administrator-controlled permissions and a request log.