Skip to content

Split Tests/UnitTests/Scripts/tests.ts into per-polyfill spec files #180

Closed

Description

@bkaradzic-microsoft

Summary

Tests/UnitTests/Scripts/tests.ts has grown to ~1.5k lines spanning 15+ describe blocks across 10+ polyfills (XHR, WebSocket, Blob, File, FileReader, TextEncoder/Decoder, URL, Console, Scheduling, AbortController, napi prototype isolation, ...). Every new polyfill grows this single file further, which hurts readability, makes ownership/blame noisy, and increases merge-conflict surface.

Proposal

Split the suite into one spec file per polyfill (e.g. Scripts/tests/xhr.ts, blob.ts, file.ts, filereader.ts, ...) with a small barrel/entrypoint that the test harness loads. Keep shared helpers (server bootstrap, fixtures) in a common module.

Context

Raised in review of #169 (File / FileReader polyfill). Filing as a standalone follow-up so that PR's diff stays focused on the polyfill itself rather than a large test reorganization.

Activity

  1. added this to the 10.0 milestone on Jun 9, 2026
  2. bkaradzic-microsoft commented on Oct 23, 2026

    @bkaradzic-microsoft
    MemberAuthor

    Implemented in #257 (commit 62818eecfb4825a70544e0159d856245fd774749): the monolithic tests.ts was replaced by feature-specific tests.*.ts files, with the native test entry points organized by feature as well. The split is present in current master. Closing this completed reorganization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions