Plan
Organise reusable test cases, sets and cycles around sprints and releases.
Nexus overview ↗Native to Jira
Test where your team works
Nexus lives in your Jira project. Use familiar issues, permissions and search to keep testing close to the work it proves.
Get started →- Jira project
- Linked issues
- Test execution
- Defect context
- Reports
Inside your Jira project
One Jira app
The whole test flow, without a second system.
Use the Jira permissions, automation and search your team already knows. Keep every test asset close to the work it proves.
Run
Execute manual, data-driven and exploratory tests with evidence and timing.
Automate
Start GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines from a cycle with Run in CI. Use the customer-hosted Nexus runner for self-hosted Jenkins or GitLab. Review results in the same cycle.
Track environments
Know what is deployed where and whether the latest evidence still applies.
Report
Use 15+ reports, Jira dashboard gadgets, scheduled digests and exports.
Execute faster
Execution Mode saves each result and moves to the next test. My Testing ranks your next actions, and Quick View drawers keep you in context.
Reuse and branch
Share steps through the Step Library, add typed step fields and data sets, and run Test Case branches before promoting them to Main.
Plan with rules
Use richer Test Plans with change history, admin-defined fields and dynamic membership, plus Sprint readiness for stories, results and open defects.
Move freely
Export folders as CSV, JSON, Excel or Cucumber .feature files. Import .feature files into folders using @folder: tags. Move Test Sets and cycles with JSON round trips or CSV exports. Preview imports and undo them if needed.
Fewer Jira API calls
Built to stay fast for large teams.
Nexus reads Jira data for the Test Repository and test case pages directly from your browser.
Quicker views
In development-build measurements, the Associations tab was about 3x faster, and repository and cycle views were up to 20% faster.
Less server work
Server-side Jira calls per test case opened fell from 40–49 to about 4. Actual timings vary with the project, network and Jira response time.
Search testing work with JQL.
Use executedBy to find runs where a person recorded a result, runsWithStatus for built-in or custom run statuses, testsInSet for set membership and requirementsWithoutTests for coverage gaps.
For example, issue in requirementsWithoutTests("ABC") finds requirements with no tests in project ABC.
Plan your Jira testing workflow
Explore Jira test case management and testing software, then follow the manual testing guide for a worked example. Use requirements traceability to review what is covered and what needs attention.