Skip to content

feat(reporter): expose failOnFlakyTests on FullConfig#40935

Open
dgozman wants to merge 1 commit into
microsoft:mainfrom
dgozman:feat-40918
Open

feat(reporter): expose failOnFlakyTests on FullConfig#40935
dgozman wants to merge 1 commit into
microsoft:mainfrom
dgozman:feat-40918

Conversation

@dgozman
Copy link
Copy Markdown
Collaborator

@dgozman dgozman commented May 20, 2026

Summary

  • Add FullConfig.failOnFlakyTests so reporters that take over stdout can explain in onEnd why a run failed (mirrors FullConfig.maxFailures).
  • Plumb it through the blob/teleport serialization so merged reports also carry it.

Fixes #40918

Reporters that take over stdout can now read `config.failOnFlakyTests`
in `onEnd` to explain why a run failed, mirroring `config.maxFailures`.

Fixes microsoft#40918
@github-actions
Copy link
Copy Markdown
Contributor

Test results for "MCP"

7181 passed, 1113 skipped


Merge workflow run.

@github-actions
Copy link
Copy Markdown
Contributor

Test results for "tests 1"

1 flaky ⚠️ [chromium-library] › library/tracing.spec.ts:432 › should produce screencast frames fit `@chromium-ubuntu-22.04-node24`

42032 passed, 850 skipped


Merge workflow run.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: promote failOnFlakyTests config to the FullConfig for reporters

2 participants