Access tokens use Atlassian Forge secret storage, are never shown again and are deleted when the connection is removed.
Test automation for Jira
Start automation from Jira and bring results back to the cycle
Run in CI starts a configured cloud pipeline from a Nexus test cycle. Your pipeline executes the tests and returns results to the same cycle.
Four cloud CI servicesFramework result integrationsCustomer-hosted runner
How it works
Run in CI from a test cycle
A project administrator connects GitHub Actions, GitLab.com, Azure DevOps Pipelines or Bitbucket Pipelines once, choosing the target, branch and pipeline or workflow. Nexus sends only the project, cycle, environment and build values the administrator selects.
A double press within 60 seconds is blocked. Every run is recorded in the audit log.
Cloud-hosted services use Run in CI. Self-hosted Jenkins or GitLab use the customer-hosted Nexus runner.
Read the service setup notes and example pipelines in the automation guide.
Implementation guide
Connect the frameworks your team uses
Results match test cases by Automation Key or issue key. Nexus records pass/fail per run, and failed runs can raise a linked Jira Bug.
Playwright uses the Nexus reporter; Selenium with pytest uses the Nexus pytest plugin.
Cypress uses a reporter or JUnit report and upload. Cucumber uses JSON report and upload.
JUnit uses XML report and upload. Mocha uses mochawesome JSON and upload. Robot Framework also works.
Jenkins jobs upload results with the same upload tool. Run automation can also queue work for the customer-hosted nexus-runner, which runs the tests and posts results back.
Implementation guide
Verify one cycle before scaling
Start with a known pass and failure. Confirm that the results attach to the intended test cases and cycle, then check the linked defect and environment context.
Create an API key with only the permissions the pipeline requires.
Set stable Automation Keys or issue keys for matching.
Keep manual and automated evidence together in the cycle.
Use the guide to configure the selected service and result upload.
Questions buyers ask
Frequently asked questions
Does Nexus run tests inside Forge?
No. Tests run in your cloud CI service or customer-hosted runner. Nexus starts the configured job and records results in Jira.
Which services can Run in CI start?
GitHub Actions, GitLab.com, Azure DevOps Pipelines and Bitbucket Pipelines. A project administrator configures the connection.
Can Jenkins publish results?
Yes. A Jenkins job uploads results with the upload tool. The customer-hosted Nexus runner can also execute queued automation and post results back.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.