CodeVetter · Repo Unpack · Testing signals
microsoft/playwright
Tests and CI were inspected, not executed; no passing result or coverage percentage is claimed. The repository uses Playwright fixtures for browser behavior and a stable runner for testing its own runner. Inspected specifications exercise success, failure, persistence, authentication redirects, and report rendering. Coverage observations are bounded to the files and ranges read, with explicit platform exclusions and CI trigger limits.
- The library config constructs separate library/page projects for Chromium, Firefox, and WebKit, excludes other-engine filenames, supports executable/mode overrides, and enables three CI retries.
- Runner tests import defineConfig from stable-test-runner; npm run ttest invokes that runner's installed CLI, and PWTEST_COVERAGE conditionally enables reporter/viewer UI coverage.
- locator-click.spec.ts covers basic/double clicks, removal of the page's Node global, and target removal during pointerup or pointerdown.
- Storage-state tests check multi-origin localStorage, replacement without extra surviving pages, malformed origins, and JSON/IndexedDB round trips; selected restore cases are marked fixme for msedge channels.
- runner.spec.ts checks duplicate-title rejection, forbidOnly errors, continuation after worker exit, and subprocess creation failure; its SIGINT test explicitly skips Windows.
- HTML reporter tests generate and inspect both directly created and intermediate-merged reports, asserting outcome counters and visibility; global-fetch tests assert authorization retention/removal and HTTPS-error option propagation.
- Primary CI defines browser/Node matrices and sharded runner jobs; the shared run-test action installs dependencies, builds, installs browsers, executes tests under Xvfb on Linux, and conditionally uploads reports. These definitions were inspected, not run.
- Test scope is conditional: BiDi excludes inspector/page-leak files and uses zero retries; Android/Electron/WebView configs reuse page suites, extension tests select Chromium, and MCP has a separate cross-platform/browser CI matrix. These definitions do not establish exhaustive executed coverage.