[api review 1.65] Failures reporter, onlyFailures and --reporter-only-failures #43794

Activity

1. Dmitry Gozman (dgozman)

   added

   feature-test-runner

   v1.65

   needs-triage

   and removed

   feature-test-runner

   v1.65

   on Oct 30, 2026
2. github-actions commented on Oct 30, 2026

   

   github-actionsBot

   on Oct 30, 2026 – with GitHub Actions · Hidden as outdated

   show commentMore actions
3. github-actions commented on Oct 30, 2026

   

   github-actionsBot

   on Oct 30, 2026 – with GitHub Actions

   Contributor

   More actions

   Hi, I'm the Playwright bot and I checked this API review item.

   Fix proposed. Removed --reporter-only-failures from both test and merge-reports, including its internal configuration override. The per-reporter onlyFailures option remains. The HTML, JSON, and JUnit documentation now explicitly says that flaky tests and their successful retries are included.

   Verification

   On Linux, using 1.65.0-next at base commit 1d5572d5ddfb7f3c8dfbbe19c8e97def0b2738db:

   • The updated command-line test failed before the change because the removed flag was still accepted. It passes with the change for both commands.
   • Existing report tests pass with onlyFailures configured separately for HTML, JSON, and JUnit, for direct runs and merged blob reports. They verify that flaky tests retain both the failed and successful attempts, while blob reports retain all tests.
   • npm run ttest -- reporter-only-failures reporter-json reporter-junit reporter-blob --workers=4: 129 passed, 3 skipped.
   • npm run build and npm run flint passed.

   These are test-runner and report-generation checks; the changed tests do not launch browsers.

   Draft PR: #43805

   _{Triaged on Linux by the Playwright bot - agent run}
4. microsoft-playwright-automation

   added a commit that references this issue on Oct 30, 2026

   fix(reporter): remove reporter-only-failures CLI flag

   ...

   4b2b2f3
5. Pavel Feldman (pavelfeldman)

   closed this as completedin #43805on Oct 30, 2026