Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Canceling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
        • Tests Performance
      • Spec Files Explorer
        • Spec Files Performance
      • Errors Explorer
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Overview
  • Setup
  • Run the tests
  • Convert the JUnit XML report
  • Upload the results
  • Example

Was this helpful?

  1. Getting Started

Others

Integrate Currents with any framework by using JUnit compatible XML reporters

PreviousTroubleshooting JestNextCI Setup

Last updated 7 days ago

Was this helpful?

Currents has flagship integrations with various testing frameworks via the dedicated reporters (like Playwright, Jest, @currents/node-test-reporter and Cypress).

Integration with other frameworks is possible by uploading a JUnit XML (or compatible) test results report to Currents using our CLI utilities from @currents/cmd package.

JUnit is an XML document used to represent the outcomes of automated tests. It is widely adopted for test reporting in CI/CD pipelines, allowing CI tools like Jenkins, GitHub Actions, ands other to parse and display test results.

JUnit reports typically contains information about:

  • Test suites - groups of test cases (e.g., a set of related tests)

  • Test cases - individual test scenarios with details like execution time, status (pass/fail), and optional logs (e.g., errors or skipped messages)

See a detailed .

Overview

A typical workflow for reporting JUnit XML results to Currents:

1

Configure testing framework

Configure your testing tool to generate the results in JUnit XML format

2

Run the tests

Run the tests and save the test results at a known location

3

Conver JUnit XML file

Run currents convert command to convert JUnit XML report to a format compatible with Currents

4

Upload the results to Currents

Run currents uploadcommand to send the results to Currents for processing

Setup

  • Install @currents/cmd package

npm i @currents/cmd

Run the tests

Refer to your framework documentation or contact Currents support for help with enabling JUnit reporter for your framework

Framework
Instructions

Vitest

NodeJS Test Runner

WebdriverIO

Cypress

Postman (Newman)

When running the tests, make sure to save the results at a known location - you will need to provide path to the generated files later.

Convert the JUnit XML report

Use currents convert command to convert JUnit format to internal Currents format. Refer to currents convert documentation for the list of supported formats and frameworks.

For example:

npx currents convert \
  --input-format=junit \
  --input-file=junit-file.xml \
  --output-dir=.currents \
  --framework=postman \
  --framework-version=v11.2.0

Upload the results

npx currents upload --project-id=xxx --key=yyy

Example

Use currents upload command to send the results to Currents. Get a and from Currents dashboard.

Check out the that demonstrates how to generate and report test results from various testing frameworks to Currents.

Record key
Project ID
example repository
Postman
Vitest
NodeJS Test Runner
WebdriverIO
https://vitest.dev/guide/reporters#junit-reporter
https://nodejs.org/api/test.html#test-reporters
https://webdriver.io/docs/junit-reporter/
https://github.com/michaelleeallen/mocha-junit-reporter
https://github.com/postmanlabs/newman?tab=readme-ov-file#junitxml-reporter
example of a complete JUnit XML file
Send results from any framework that supports JUnit XML format