Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Web Test Runner

modern-web.dev

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • Self-hosted
8.3 Club score Visit modern-web.dev

What Web Test Runner is

Web Test Runner is a free, open-source test runner for web applications, installed as an npm development dependency. It runs test files in parallel and in separate browser environments. Its documented browser launchers include Puppeteer, Playwright, Selenium, BrowserStack, and WebdriverIO; Playwright supports Chromium, Firefox, and WebKit, while BrowserStack can run tests remotely, including on older browser versions. For debugging, it can open a real browser window with developer tools and report browser logs, 404 responses, and errors. The command line offers interactive watch mode, which reruns tests when files change, and code coverage with configurable thresholds and reports. Default coverage instrumentation uses Chromium. Other capabilities include mocking ES modules through import maps and integrating Mocha, with guidance for creating a custom test framework. The project is powered by esbuild and Rollup plugins and is MIT-licensed. Its documentation points users to GitHub for help and feedback.

Who it suits

It suits web developers who want browser-based testing with parallel runs, debugging, and coverage reporting. Teams needing remote browser runs can use its documented BrowserStack launcher.

Good to know, and what to watch

  • Runs test files in parallel and isolation
  • Playwright supports Chromium, Firefox, and WebKit
  • Watch mode reruns tests when files change
  • Reports browser logs, 404 responses, and errors
  • MIT-licensed and installable through npm
  • Default coverage instrumentation uses Chromium
  • BrowserStack remote testing requires its documented launcher

Open source

Free

Free plan

Getting started

  1. Open the Modern Web documentation website
  2. Install @web/test-runner as an npm development dependency
  3. Choose a documented launcher such as Puppeteer, Playwright, Selenium, BrowserStack, or WebdriverIO
  4. Configure a Mocha integration or custom test framework
  5. Run tests from the command line and enable watch mode or coverage as needed

The Club's review

Web Test Runner is an open-source test runner for web applications, aimed at developers who want tests to execute in browsers rather than only in a simulated environment. It is a strong fit for browser-focused projects that need isolated runs and flexible launcher choices; teams should weigh its Chromium-based default for coverage against their target-browser needs.

Overview

Installed as an npm development dependency, Web Test Runner runs test files in parallel, each in its own browser environment. That separation helps prevent one file’s browser state from affecting another, while watch mode reruns tests when files change. These capabilities suit active development on web applications, though teams still need to choose and configure an appropriate browser launcher.

Modern Web publishes the project under the @web npm namespace and describes its code as open source. The GitHub repository is MIT-licensed. The project directs users to GitHub for help and feedback, and welcomes documentation contributions; Discord is available for community discussion.

Key features

Browser execution and diagnostics

Documented launchers include Puppeteer, Playwright, Selenium, BrowserStack, and WebdriverIO. Playwright supports Chromium, Firefox, and WebKit, letting teams exercise several browser engines. BrowserStack adds remote execution and can be useful for checking older browser versions. This breadth is valuable when browser behavior is central to a project, but it also makes launcher choice part of the setup rather than a fixed, one-size-fits-all path.

Debug mode opens a real browser window with developer tools. The runner also reports browser logs, 404 responses, and errors, which gives developers useful context when a failure involves browser activity or missing resources. Those diagnostics make it more practical to investigate browser-specific failures than relying on a pass/fail result alone.

Watch mode, coverage, and mocking

Interactive watch mode and code coverage profiling are available from the command line. Coverage supports configurable thresholds and reports, so teams can incorporate coverage expectations into their workflow. Its default instrumentation uses Chromium, however, which is worth considering when Firefox or WebKit coverage is important.

Web Test Runner can mock ES modules through import maps. The project is powered by esbuild and Rollup plugins, and its documentation covers a Mocha integration as well as instructions for building a custom test framework. That framework flexibility can suit projects with established testing preferences, though it may require more setup than adopting a single prescribed framework.

The documentation also describes running the Playwright launcher in GitHub Actions with Microsoft’s Playwright Action, a concrete route for teams using that CI environment.

Pricing

Web Test Runner is free and open source. Its Open source plan costs nothing and is MIT-licensed; installation is as an npm development dependency. There are no paid tiers or seat-based terms to weigh in the published plan. The project supports component testing, snapshot testing, and coverage reporting, with Chromium, Firefox, and WebKit supported runtimes.

Platforms

The project supports Linux, macOS, Windows, web, and self-hosted environments. Its documented Playwright launcher covers Chromium, Firefox, and WebKit, while BrowserStack supports remote runs. The available browser and launcher choices make it adaptable to local and remote browser testing, but coverage’s default Chromium instrumentation remains a consideration for cross-browser coverage workflows.

Who it's for

Web Test Runner is best suited to developers and teams building web applications who want tests to run in browser environments, with parallel isolated files, watch mode, and diagnostics. It is particularly relevant when the project needs to exercise multiple browser engines or use a remote launcher. Teams seeking a minimal setup around one predefined test framework may prefer a more prescriptive tool; Web Test Runner documents Mocha and custom-framework paths instead.

Pros and cons

  • Pro: Parallel execution gives each test file its own browser environment, helping keep files isolated.
  • Pro: Playwright supports Chromium, Firefox, and WebKit, and BrowserStack enables remote runs, including older browser versions.
  • Pro: Debug mode, browser logs, 404 reporting, and error reporting offer useful clues when investigating failures.
  • Pro: Watch mode, configurable coverage thresholds, import-map module mocking, and framework guidance cover several common development needs.
  • Con: Coverage instrumentation defaults to Chromium, which may not align with projects prioritizing other browsers.
  • Con: Multiple launchers and framework choices offer flexibility but leave teams to select and configure their preferred testing setup.

Alternatives

For a wider comparison, browse JavaScript Testing Frameworks.

Karma is another free, MIT-licensed option, but it is deprecated and receives no new features or general bug fixes. QUnit is a free open-source JavaScript testing framework distributed through CDN, npm, and Yarn. Vitest is a free, open-source alternative with no plan limits stated. Cucumber.js is available as an npm module for installation as a development dependency. Pure Test is free Apache-2.0 open-source software. Testem is a free, MIT-licensed open-source JavaScript test runner. Rstest is a free, MIT-licensed JavaScript/TypeScript testing framework. uvu is a free, MIT-licensed test runner for Node.js and the browser.

Verdict

Choose Web Test Runner if your web application needs real-browser execution, isolated parallel files, and a choice of local or remote launchers without a software license cost. Its browser diagnostics and flexible framework integration strengthen that case. Look elsewhere if your coverage workflow must default to a browser other than Chromium or you want a more prescriptive framework setup.

The verdict

Web Test Runner combines browser launchers, diagnostics, watch mode, and coverage in a free, open-source project. Its browser and coverage options are clearly documented, though default coverage instrumentation uses Chromium.

Questions people ask

Is Web Test Runner free?

Yes. The listed Open source plan is free, and the project is MIT-licensed.

Which browsers can it run?

The Playwright launcher supports Chromium, Firefox, and WebKit. Other documented launchers include Puppeteer, Selenium, BrowserStack, and WebdriverIO.

Can it run tests remotely?

Yes. The BrowserStack launcher runs tests remotely and is described as useful for older browser versions.

Does it provide coverage reports?

Yes. Coverage supports configurable thresholds and reports, with Chromium used for default instrumentation.

How can tests be debugged?

Debug mode opens a real browser window with developer tools and reports browser logs, 404 responses, and errors.

What the maker publishes

Browser coverage
The Playwright launcher supports bundled Chromium, Firefox, and WebKit browsers. source
Browser diagnostics
It reports browser logs, 404 responses, and errors. source
Browser integrations
Playwright can run tests on Chromium, Firefox, and WebKit; BrowserStack and Sauce Labs launchers are also documented. source
Browser launchers
Documented launchers include Puppeteer, Playwright, Selenium, BrowserStack, and WebdriverIO. source
Browser testing
It can run tests in headless browsers using Puppeteer, Playwright, Selenium, or WebdriverIO. source
Build tooling
The runner is powered by esbuild and Rollup plugins. source
Code coverage
Coverage supports configurable thresholds and reports, while the default coverage instrumentation uses Chromium. source
Debugging
Debug mode opens a real browser window with developer tools, and the runner reports browser logs, 404s, and errors. source
Debugging
Debug mode opens a real browser window with developer tools. source
Execution
Tests run in parallel and isolation, and watch mode reruns tests when files change. source
Installation
The project documents installation as an npm development dependency using @web/test-runner. source
Installation
The official installation instructions use npm to add @web/test-runner as a development dependency. source
Integrations
The docs describe using the Playwright launcher with GitHub Actions via Microsoft's Playwright Action. source
License
The project's GitHub page identifies the repository license as MIT. source
Maker
Modern Web describes its goal as providing developers with guides and tools for modern web development while working closely with the browser. source
Maker focus
Modern Web says its goal is to provide developers with guides and tools for building for the modern web while working closely with browser capabilities. source
Module mocking
The runner can mock ES modules using import maps. source
Module mocking
The runner can mock ES modules using import maps. source
Parallel and isolated tests
Tests run in parallel and in isolation, with each test file in its own browser environment. source
Project status
Modern Web says its code is open source and publicly available on GitHub, with packages published under the @web npm namespace. source
Purpose
Web Test Runner is a test runner for web applications. source
Purpose
Web Test Runner is a test runner for web applications. source
Remote testing
The BrowserStack launcher runs tests remotely, and the docs say it can be useful for older browser versions. source
Support
The project links to Discord for community discussion and lists sponsorship and contributions as ways to support it. source

Checked against the maker's pages on 3 Oct 2026.