Your stack.
Connected.

Playwright reporter

For Playwright Test. It sends the whole run at the end, so you don't need an extra pipeline step. Node 18+, Playwright 1.40+, no other dependencies.

Install

npm install --save-dev https://nexus.resync.nz/downloads/nexus-playwright-reporter-0.2.3.tgz

Configure

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['list'],
    ['@resyncnz/nexus-playwright-reporter', { project: 'NEX', environment: 'staging' }],
  ],
});

The URL and key come from NEXUS_URL and NEXUS_API_KEY. Other options: testSet, component, failOnUploadError (fail the run if the upload fails; off by default) and enabled (for example !!process.env.CI).

Example

test('NEX-12: mandatory fields show validation errors', async ({ page }) => { ... });

Put the key on the test's own title, not on a describe block.

pytest plugin

For pytest, including Selenium suites. It sends the session's JUnit XML report when the run ends. Python 3.8+, pytest 7+, no other dependencies.

Install

pip install https://nexus.resync.nz/downloads/pytest_nexus-0.2.3-py3-none-any.whl

The plugin loads by itself and does nothing until a Nexus URL is set.

Configure and run

export NEXUS_URL=...        # from your CI secrets
export NEXUS_API_KEY=...
pytest --nexus-project NEX --nexus-environment staging

Other options: --nexus-test-set, --nexus-component, --nexus-fail-on-upload-error and --no-nexus. If you already pass --junitxml, that file is the one sent.

Example

def test_NEX_11_valid_user_signs_in(driver):
    ...

Python names can't contain -, so use _. Nexus reads NEX_11 as NEX-11.

GitHub Action

For GitHub Actions, with any results file. It needs only bash and curl, so it runs on Linux, macOS and Windows runners. You keep a copy in your repository.

Install

Unzip it into .github/actions/nexus-upload and commit the folder:

mkdir -p .github/actions/nexus-upload
curl -fsSLo nexus-action.zip https://nexus.resync.nz/downloads/nexus-github-action-0.3.4.zip
unzip -o nexus-action.zip -d .github/actions/nexus-upload && rm nexus-action.zip
git add .github/actions/nexus-upload

Configure

Add NEXUS_URL and NEXUS_API_KEY under Settings → Secrets and variables → Actions in GitHub.

Example

    steps:
      - uses: actions/checkout@v4
      # ... run your tests, writing results.xml ...
      - name: Send results to Nexus
        if: ${{ always() }}
        uses: ./.github/actions/nexus-upload
        with:
          url: ${{ secrets.NEXUS_URL }}
          api-key: ${{ secrets.NEXUS_API_KEY }}
          project: NEX
          file: results.xml
          environment: staging

if: always() sends the results even when tests fail. Those are the runs you most want recorded. Set fail-on-error: 'false' if an upload problem should only warn.

Upload CLI

For any CI system and any results file: JUnit XML, xUnit XML, NUnit XML, TestNG XML, Robot Framework XML, Cucumber JSON, Mocha JSON, mochawesome JSON, Playwright JSON or Postman/Newman JSON. It detects the format for you. One file, no dependencies, Node 16+.

Install

Download the script in your CI job, and check it if you like:

curl -fsSLo nexus-upload.mjs https://nexus.resync.nz/downloads/nexus-upload-0.3.4.mjs
echo "8aeaad9b8710d88c3688d8a1fe3ad00ef897a982e8ab79475f6390b55270f88f  nexus-upload.mjs" | sha256sum -c -

Or add the npm package to your project: npm install --save-dev https://nexus.resync.nz/downloads/nexus-upload-0.3.4.tgz, then run npx nexus-upload.

Example

export NEXUS_URL=...        # from your CI secrets
export NEXUS_API_KEY=...
node nexus-upload.mjs results.xml --project NEX --environment staging

Other options: --test-set, --component, --format, --soft (warn but exit 0) and --dry-run. Run node nexus-upload.mjs --help for the full list. Exit codes: 0 sent, 1 Nexus refused the file or couldn't be reached, 2 a usage or file problem.

Cypress plugin

For Cypress. It sends the whole run when Cypress finishes (after:run), with each failure's error and stack. Node 18+, Cypress 12+, no other dependencies.

Install

npm install --save-dev https://nexus.resync.nz/downloads/nexus-cypress-0.1.2.tgz

Configure

// cypress.config.js
const { defineConfig } = require('cypress');
const nexus = require('@resyncnz/nexus-cypress');

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      nexus(on, config, { project: 'NEX', environment: 'staging' });
      return config;
    },
  },
});

The URL and key come from NEXUS_URL and NEXUS_API_KEY. Other options: testSet, component, failOnUploadError and enabled. If another plugin also uses after:run, call sendResults(results, options) from your own handler instead.

Example

it('NEX-12: mandatory fields show validation errors', () => { ... });

Azure DevOps task

For Azure Pipelines. A pipeline task, NexusUpload@0, that sends one or more results files. It keeps the key in Azure's secret masker and marks the step "Succeeded with issues" rather than failing when you ask it to.

Install

Unzip it and upload the task to your Azure DevOps organisation once, with Microsoft's tfx tool and a personal access token that can manage agent pools:

unzip nexus-azure-devops-task-0.1.2.zip -d nexus-task
npx tfx-cli build tasks upload --task-path nexus-task/NexusUpload \
  --service-url https://dev.azure.com/YOUR-ORG --auth-type pat --token YOUR-PAT

Configure

Add NEXUS_URL and NEXUS_API_KEY as secret pipeline variables.

Example

  - task: NexusUpload@0
    displayName: Send results to Nexus
    condition: succeededOrFailed()
    inputs:
      resultsFiles: '**/results.xml'
      nexusUrl: $(NEXUS_URL)
      apiKey: $(NEXUS_API_KEY)
      project: NEX
      environment: staging

Other inputs: format, testSet, component, stepMatching, systemOut, failOnError and failIfNoFiles. Prefer not to install a task? Use the upload CLI example instead.

Nexus runner

Lets testers start your automated tests from a Nexus cycle with Run automation. The runner runs where your tests already run (a laptop, a CI agent or a container), asks Nexus for queued runs, runs your test command and posts the results back. Nexus never connects to your machines. One file, no dependencies, Node 18+.

Set up

1. In Jira, open Project settings → Nexus → Automation. It builds the config for each of your test tools and shows the runner URL.
2. Save the runner and the config (as nexus-runner.config.json) next to your tests, and set NEXUS_API_KEY.
3. Check the setup, then start it:

node nexus-runner.mjs --test     # checks the config and the connection
node nexus-runner.mjs            # keeps polling for queued runs
node nexus-runner.mjs --once     # one poll, for a scheduled CI job

Nexus requires runner 0.6.2 or later. To upgrade, replace nexus-runner.mjs with the newest file here.