Use a single representative test for the first delivery.
Playwright testing in Jira
Connect Playwright tests to Jira test cases
Keep your Playwright suite and browser infrastructure. The Nexus reporter sends results to Jira Test Cases, giving testers and engineers a shared place to inspect the outcome.
Playwright reporterExisting Jira Test CasesYour workstation or CI runner
How it works
Start with one case and one browser test
Choose a small Playwright test that already passes in your environment. Open its corresponding Nexus Test Case, set a unique Automation Key and make sure the case is Ready. Put that key at the beginning of the individual Playwright test title, for example NEX-12: valid user signs in. A key in the enclosing describe block alone is not the documented setup.
The matching Test Case must already exist in the same Jira project. Renaming a browser test does not create a case or link it to a requirement. Record that relationship in Nexus so a reviewer can follow the requirement through its test and execution evidence.
Choose a stable Automation Key and keep it unique.
Put the key on the individual test title.
Check that the Jira case is Ready before running it.
Implementation guide
Add the reporter to your existing configuration
Install the Nexus Playwright reporter from the Playwright setup instructions. Add it to the reporter array in your existing playwright.config.ts; retain the projects, browser settings, fixtures and other reporters your suite needs. Playwright supports multiple reporters, so Nexus delivery can sit alongside terminal or HTML reporting.
Set failOnUploadError: true for the Nexus reporter when you want a failed delivery to fail the run. Without this option, upload errors produce warnings. This distinction matters when a passing browser test could otherwise leave Jira without a result. The linked setup guide contains the installation command and configuration to copy.
Keep the existing application and browser setup.
Use the published reporter package and configuration.
Retain local reporters for normal investigation.
Choose deliberately how upload failures affect the job.
Implementation guide
Supply connection values to the test process
In Nexus project CI settings, create an ingest key with Send results permission and copy the complete results URL. Expose these as NEXUS_API_KEY and NEXUS_URL to the process running Playwright. Use NEXUS_PROJECT for the Jira project key, NEXUS_ENVIRONMENT for the environment label and, optionally, NEXUS_TEST_SET for an existing cycle.
For local checks, use the terminal prompts in the automation guide. For unattended runs, store credentials in the CI provider secret store. The reporter sends results at the end of the run: do not add a second upload step for that same report. Browser execution remains on your computer or CI runner; Nexus receives the evidence.
Use the results URL, not a Jira site address or the separate CI API URL.
Use a Nexus ingest key, not an Atlassian account token.
Give the test process access to the intended CI secrets.
Send each report once to avoid duplicate executions.
Implementation guide
Verify delivery before expanding the suite
Run only the keyed test first. HTTP 202 means Nexus accepted the submission for background processing; it does not prove that every result matched. Inspect the CI delivery log, then open the expected Test Case execution and check its status, environment and cycle.
If the result is missing, check the individual title, unique key, Ready status, project and secret availability. If executions appear twice, inspect both reporter configuration and pipeline upload steps. Once the small example works, expand the suite and review failures through the normal Jira traceability workflow. Keep Playwright traces and other debugging artifacts in your established CI process.
Confirm accepted delivery and a matched result.
Compare the recorded outcome with the actual browser run.
Check the intended environment and optional cycle.
Investigate missing or duplicate results before increasing scope.
Questions buyers ask
Frequently asked questions
Does Nexus execute Playwright inside Jira?
No. Playwright runs on your workstation or CI runner. Nexus receives results and records them against existing Jira Test Cases.
Do I need a separate upload step with the reporter?
No. The Nexus reporter sends the results. A second upload for the same run can create duplicate executions.
Does a Playwright test title create a Jira test case?
No. Create or import the Nexus Test Case first, make it Ready and use its unique Automation Key in the individual test title.
Test the workflow with a real Jira project
Start with one requirement, one cycle and one release decision.