Upload JUnit, Cucumber, Playwright, Mocha, xUnit and Nexus JSON results.
Test automation for Jira
Connect test automation to Jira without moving execution into Jira
Keep Playwright, Cypress, pytest, JUnit and other test execution in your environment. Nexus receives results, links them to Jira work and shows manual and automated evidence together.
Customer-hosted executionCI result ingestionOne evidence model in Jira
How it works
Jira is the control plane, not the test runtime
Forge does not run browsers or test suites. Your existing CI agent, workstation or container runs the tests. Nexus issues API credentials, queues configured jobs for your runner and ingests the resulting report.
Use packaged helpers for Playwright, pytest, Cypress, GitHub Actions and command-line uploads.
Match results through stable automation keys instead of brittle test names.
Keep failure evidence, retries, defects and environment context together.
Implementation guide
A rollout path that protects signal quality
Begin with one pipeline and one suite. Confirm test matching, duplicate handling, environment names and failure evidence before scaling to more repositories.
Create a least-privilege CI API key.
Upload one known pass and one known failure.
Confirm both results attach to the intended Jira Test Cases.
Verify a repeated failure updates the expected open defect policy.
Add the runner only when Jira-triggered execution is part of the workflow.
Questions buyers ask
Frequently asked questions
Does Nexus execute Playwright inside Forge?
No. Automation runs in infrastructure you control. Nexus ingests results or coordinates work through the customer-hosted runner.
Can existing CI pipelines publish results?
Yes. The CI API and packaged upload tools are designed for existing pipelines.
Do manual and automated results appear together?
Yes. They share the same execution, traceability and reporting model.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.