Closed Bug 2006813 Opened 5 months ago Closed 1 month ago

[wpt-sync] Sync PR 56840 - feat(manifest): Add initial tooling for Test262 test types

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox151 fixed)

RESOLVED FIXED
151 Branch
Tracking Status
firefox151 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 56840 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/56840
Details from upstream follow.

wpt-pr-bot <wpt-pr-bot@users.noreply.github.com> wrote:

feat(manifest): Add initial tooling for Test262 test types

This commit introduces the foundational infrastructure for the WPT manifest to recognize and process Test262 ECMA-262 conformance tests. This is the first step towards the goal of running the entire Test262 suite within the WPT infrastructure, as outlined in the approved RFC.

The core of this change is a new TestRecord parser in test262.py which is responsible for extracting the YAML frontmatter from Test262 .js files. This metadata is then used by the manifest generation process to correctly identify and classify the tests.

Key changes included in this commit:

  • A new tools/manifest/test262.py module containing the YAML frontmatter parser.
  • A corresponding Test262Test manifest item type defined in tools/manifest/item.py to represent these tests.
  • Updates to tools/manifest/sourcefile.py to identify Test262 files by their directory path (/test262/) and invoke the new parser.
  • The addition of pyyaml as a project dependency to handle the YAML parsing to tools/wpt/requirements.txt
    • Note to reviewers: PyYaml is lazily loaded. This is to prevent the modification of too many commands.json files. This may not be preferred since WPT does not do that often but open to other options. Please check failing checks for commits on the original PR for how I kept trying to track down the next commands.json file to fix.
  • New unit tests for the parser and the manifest generation logic for Test262 files.

This work is part of the effort to add Test262 support as laid out in the RFC: https://github.com/web-platform-tests/rfcs/pull/229

This commit is the first in a series of smaller PRs split from the larger, original implementation in https://github.com/web-platform-tests/wpt/pull/55997. Subsequent PRs will add the server-side logic to serve the tests and the wptrunner integration to execute them.

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/9c57951df6ca https://hg.mozilla.org/integration/autoland/rev/2e83cf2f25e5 [wpt PR 56840] - feat(manifest): Add initial tooling for Test262 test types [pt 1/5], a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
Test result changes from PR not available.
You need to log in before you can comment on or make changes to this bug.