Cucumber.js vs QUnitX

Cucumber.js checks software against executable specifications written as plain-text scenarios, reporting whether each scenario passes or fails. It is the JavaScript implementation of Cucumber and runs on Node.js. Scenarios use Gherkin syntax and are usually kept in `.feature` files alongside the software in source control. Step definitions connect each Gherkin step to code that carries out its described action; expressions can use Cucumber Expressions or regular expressions, but not both syntaxes in a single expression.

The tool runs feature files from the command line and can run in continuous integration, including parallel execution. Reporter plugins can produce results, and reports can be published to Cucumber Reports with `--publish`. Published reports are public and deleted after 24 hours. Cucumber.js is available as the `@cucumber/cucumber` npm module, installed as a development dependency with npm or Yarn. The setup requires Node.js and one of those package managers. It is free and open source, with Linux, macOS, Windows, and self-hosted platforms listed. It works with browser automation tools, but is not itself one.

QUnitX lets teams write JavaScript or TypeScript tests in one file and run them with Node.js, Deno, or in a browser. The project says it needs no configuration files, transform pipeline, injected globals, or runtime dependencies, and that TypeScript runs as-is. Its assertions cover deep and partial equality, error matching, ordered steps, assertion counts, and per-test timeouts. Tests can be organized in nested modules with before, beforeEach, afterEach, and after hooks. The browser interface filters tests, shares filtered views by URL, reruns individual tests, and displays assertion differences. The linked qunitx-cli runs tests in headless Chromium, Firefox, or WebKit and streams TAP output. It also supports esbuild plugins, GitHub-annotated output, JUnit XML, V8 coverage reports, and a JavaScript API. QUnitX is free and lists an MIT license. The core requires Node.js 22 or later or Deno 2 or later; the CLI requires Node.js 24 or later or Deno 2.7 or later. Its default standalone Chromium mode also needs system Chrome or CHROME_BIN. Browser coverage has a source-map limitation.