fleet-running-test262

To run test262 conformance across parser runtimes, you need automated orchestration that coordinates each repository's canonical runner script and aggregates the results. This skill automates that cross-fleet execution to surface non-conforming behavior.

Comparing TC39 test262 results requires enforcing a single source of truth for submodule pins and runner scripts. This skill enforces those pins to ensure apples-to-apples comparisons across multiple parser implementations.

Cross-fleet test262 orchestration manages unsupported features through configurable runner invocation. This skill coordinates per-repo runner scripts to handle unsupported features and surfaces non-conforming behavior for debugging.

Yes, pinned submodules are required to validate test262 conformance accurately. This skill enforces a single source of truth for test262 submodule pins to ensure consistent, auditable test orchestration across all parser runtimes.

Yes, you can use this for release readiness benchmarking with TC39 test262. It identifies non-conforming behavior and aggregates results across multiple parser implementations to support debugging and release validation.