Design reusable tests, run manual and automated checks, and follow every result back to its requirement, data and release context.
Get started →
The whole quality story
01 / Execution
Run tests step by step inside Jira. Capture evidence, record actual results and create a linked defect the moment something fails.
02 / Traceability
Trace every requirement to its tests, results and defects. Bring in CI results and see manual and automated evidence together.
Run in CI starts your configured GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines pipeline. An administrator connects the service once and chooses which project, cycle, environment and build values Nexus sends. Your pipeline executes the tests and uploads results to the same cycle.
Self-hosted Jenkins and GitLab use the customer-hosted Nexus runner. Jenkins jobs can also upload reports directly.
Set up the full automation workflow →
Format steps, preconditions and free-text cases with bold, italic, inline code, code blocks, lists and links, using a toolbar and preview. Existing plain cases are unchanged until formatting is enabled.
Export a folder with or without its sub-folders as CSV, JSON, Excel or Cucumber .feature files. Import .feature files using @folder: tags. Test Sets and cycles support JSON round trips and CSV export. Imports preview first and can be undone.
The separate Read test data API permission is off by default. A scoped project key can read paged cases, cycles, runs, step results and coverage as JSON. Issue-security records are excluded and sensitive test data values are masked.
Use the manual test execution guide to create cases, run a cycle and record defects. Connect test automation from Jira to the same cycle, then use requirement-to-test traceability to review coverage. Explore the complete Jira test management workflow.
My Testing brings your execution, review and failure follow-up into one personal view. Quick View drawers show related runs, cases, defects and requirements without losing your place. Start or resume Execution Mode from a cycle or your testing work, save a result and move to the next test. Nexus remembers your place per cycle.
Project administrators curate the Step Library. Insert linked steps into a case, review the impact before applying shared updates, or detach a local variation. Typed step fields capture structured dates, choices and people. Where Test Case branches are enabled, compare an alternative design, run it alongside Main and promote it with a reason and conflict check.
Test Plans carry scope, strategy, status, comments, links, history and administrator-defined fields. Dynamic membership uses rules or JQL; preview the selection and start a cycle from one recorded generation. Closing a plan freezes its membership.
Choose Execute offline to export an Excel or CSV worksheet, optionally including test steps. Testers can complete it outside Jira; an authorised Jira user imports the results, reviews conflicts and applies them. Control distribution of the exported data through your organisation's policies.
