Skip to content

doc: update WPT test runner README.md#62680

Open
panva wants to merge 2 commits intonodejs:mainfrom
panva:wpt-readme
Open

doc: update WPT test runner README.md#62680
panva wants to merge 2 commits intonodejs:mainfrom
panva:wpt-readme

Conversation

@panva
Copy link
Copy Markdown
Member

@panva panva commented Apr 10, 2026

  • Rewrite introduction; remove outdated test-whatwg-* note and redundant "How it works" section
  • Document full WPTRunner API (concurrency, setFlags, setInitScript, setScriptModifier, pretendGlobalThisAs)
  • Switch all examples from JSON to CJS
  • Document wildcard * patterns in status file keys
  • Document inspector as a supported requires value
  • Add "Daily WPT report" section with wpt.fyi dashboard link

Signed-off-by: Filip Skokan <panva.ip@gmail.com>
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/web-standards

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Apr 10, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.93%. Comparing base (de5644c) to head (019f97b).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #62680      +/-   ##
==========================================
- Coverage   89.81%   88.93%   -0.89%     
==========================================
  Files         699      699              
  Lines      216235   216235              
  Branches    41336    41246      -90     
==========================================
- Hits       194216   192302    -1914     
- Misses      14129    15970    +1841     
- Partials     7890     7963      +73     

see 105 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

### 1. Create a status file

For example, to add the URL tests, add a `test/wpt/status/url.json` file.
For example, to add the URL tests, add a `test/wpt/status/url.cjs` file.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we mean to encourage use of CJS over JSON? Shouldn't we give the two examples?

Suggested change
For example, to add the URL tests, add a `test/wpt/status/url.cjs` file.
For example, to add the URL tests, add a `test/wpt/status/url.json` or `test/wpt/status/url.cjs` file.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we mean to encourage use of CJS over JSON?

For the features available, yes. As it is much less destructive wrt to WPT status file backports to avoid switching from json to cjs as much as possible.

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. and removed needs-ci PRs that need a full CI run. labels Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants