QUnit Test Output Parser

Warnings

• breaking This package is effectively abandoned, with its last publish occurring over seven years ago. There are no recent updates, bug fixes, or security patches. It is highly unlikely to be compatible with modern QUnit versions, Node.js runtimes, or contemporary JavaScript module systems without significant intervention or polyfills.
  Fix: Consider using alternative methods for processing QUnit results, such as QUnit's built-in `QUnit.on()` reporter events (which provide programmatic access to test results) or robust external test report parsers (e.g., JUnit XML reporters and parsers) if an intermediate file format is acceptable.
• gotcha Due to its age, `qunit-parser` was written for CommonJS environments. Attempting to use ES Modules (`import`) directly will likely result in a `TypeError: require is not a function` or similar module resolution errors in modern Node.js environments configured for ESM, or build failures in bundlers.
  Fix: Ensure your project is configured for CommonJS, or use dynamic `import()` for ESM projects (`import('qunit-parser').then(mod => { const { parse } = mod; ... })`), though full functionality is not guaranteed given the package's age.
• gotcha Parsing raw console output is inherently brittle. The `qunit-parser` likely relies on specific output formats from QUnit that may have changed significantly over time. Any minor change in QUnit's console reporter format (e.g., different wording, new lines, different formatting of objects) could break the parser entirely, leading to incorrect or incomplete results.
  Fix: If possible, prefer programmatic access to QUnit results using QUnit's event system (e.g., `QUnit.on('testEnd', handler)`) or by generating a standardized report format like JUnit XML (using a QUnit reporter plugin) and parsing that, as these methods are generally more robust than parsing raw text.

Install

• npm install qunit-parser npm
• yarn add qunit-parser yarn
• pnpm add qunit-parser pnpm

Imports

• parse
  wrong:

  import { parse } from 'qunit-parser';

  correct:

  const { parse } = require('qunit-parser');

  This package is very old (v0.2.0, last updated 7+ years ago) and primarily supports CommonJS `require()`. ESM `import` syntax is unlikely to work directly without transpilation or specific build configurations.

Quickstart

Demonstrates how to import the `qunit-parser` and use it to process a simulated QUnit console output string, showing the structured data that can be extracted.

const { parse } = require('qunit-parser');

// Simulate a simplified QUnit console output string
const qunitOutput = `
Running 2 tests
ok 1 - My Module > Test 1: should pass
# pass 1
# fail 0
not ok 2 - My Module > Test 2: should fail an assertion
# test timed out
# {
#   "name": "My Module > Test 2: should fail an assertion",
#   "passed": 0,
#   "failed": 1,
#   "total": 1,
#   "duration": 50,
#   "errors": ["Assertion failed: expected true, got false"],
#   "seed": "12345"
# }
1..2
# tests 2
# pass 1
# fail 1
`;

try {
    const parsedResults = parse(qunitOutput);
    console.log('Parsed QUnit Results:');
    console.log(JSON.stringify(parsedResults, null, 2));
    // Example of accessing parsed data
    console.log(`Total tests: ${parsedResults.total}`);
    console.log(`Passed tests: ${parsedResults.passed}`);
    console.log(`Failed tests: ${parsedResults.failed}`);
    if (parsedResults.failures && parsedResults.failures.length > 0) {
        console.log('Details of first failure:', parsedResults.failures[0]);
    }
} catch (error) {
    console.error('Error parsing QUnit output:', error.message);
}