npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

junit-converter

v1.0.5

Published

Test report files to JUnit XML converter

Readme

Test report files to JUnit converter

Actions Status Git Issues Closed Issues

Overview

  • Convert test report files to JUnit format.

Supported report formats

  • JUnit/xUnit XML Format
  • NUnit v3+ XML Format
  • xUnit.net v2+ XML Format
  • MSTest TRX Format

Conversion process

  • All test reports are first converted to JUnit format using XSLT.
  • Any nested test suites are flattened.
  • TRX files undergo additional processing to enhance JUnit output.

JUnit

  • Flattens any nested test suites.

NUnit

  • NUnit v3+ XML is supported.
  • Converts <properties> elements to JUnit <properties>.
  • Converts <output> elements to JUnit <system-out>.
  • Converts skipped test-case <reason> elements to JUnit <skipped> with message.
  • Converts test-case <failure> elements to JUnit <failure> with message and stack trace.

xUnit.net

  • xUnit.net v2+ XML is supported.
  • Converts <traits> elements to to JUnit <properties>.
  • Converts skipped test <reason> elements to JUnit <skipped> with message.
  • Converts test <failure> elements to JUnit <failure> with message and stack trace.
  • Supports single <assembly> per file, if multiple assemblies are present, only the first will be converted.

MSTest TRX

dotnet test generates TRX style files unless different logger is used.`

  • Converts Output/ErrorInfo/ErrorInfo to JUnit <failure> with message.
  • Converts Output/ErrorInfo/Message to JUnit <failure> message.
  • Converts Output/ErrorInfo/StackTrace to JUnit <failure> stack trace.
  • Converts Output/StdErr to JUnit <system-err>.
  • Converts Output/StdOut to JUnit <system-out>.
  • Converts Inconclusive and NotExecuted tests to <skipped> with message.
  • Tests are split into multiple <testsuite> elements by test classname.
  • Tests are ordered by name.
  • Test suit times are not 100% accurate - displayed as a sum() of all test times.

Usage

npm i --save-dev junit-converter
const converter = require('junit-converter');

let options = {
    testFile: 'mytesfiles/nunit.xml',
    testType: 'nunit'
}

// Convert test report to JUnit format and save to file
// Set minify:true to save minified XML
converter.toFile(options).then(() => console.log(`JUnit report created`));

// Convert test report to JUnit format and return as 'pretty' XML string
// Set minify:true to returm minified XML string
converter.toString(options).then((result) =>{/*do something with result*/});

// Convert test report to JUnit format and return as JSON object for processing
converter.toJson(options).then((result) =>{/*do something with result*/});

CLI usage

npm i -g junit-converter

Convert test report to JUnit format and save to file

junit-converter --testFile mytests/nunit.xml --testType nunit

Options

| Option | Type | Default | Description | |:--------------------------|:--------|:--------------------------|:--------------------------------------------------| | testFile (required) | string | | Path to test file for conversion | | testType (required) | string | | Test report type | | reportDir | string | ./report | Converted report output path when saving file | | reportFile | string | testFile.name-junit.xml | JUnit report file name | | splitByClassname | boolean | false | Split into multiple test suites by test classname | | minify | boolean | false | Minify XML result |

  • testFile - relative or absolute path to input test file.
  • testType - type of test report, not case-sensitive.
  • reportDir - will be created if path does not exist. Only used when saving to file.
  • reportFile - JUnit file name. Only used when saving to file.
  • splitByClassname - If true, splits test cases into multiple test suites by classname.
    This is useful for test runners that generate tests under a single test suite such as dotnet test when using JUnit loggers.
    Should only be set to true if test report file contains single test suite. TRX report files are always split by classname, so this option is ignored for TRX files.

Supported testType options.

| testType | File Type | |:-----------|:------------------| | JUnit | JUnit/xUnit XML | | NUnit | NUnit v3+ XML | | xUnit | xUnit.net v2+ XML | | TRX | MSTest TRX |