🚀 Feature Request
Move failOnFlakyTests from the internal config to the public config so reporters that take over stdout can reason about why the run failed in the output.
Similar to maxFailures.
Example
Similar to maxFailures, reporters that print to stdout should be able to reason about why a run failed in their onEnd.
Here is an example printer snippet that uses maxFailures:
const stoppedEarly = [];
if (
this.pwConfig.maxFailures &&
failedTests.length >= this.pwConfig.maxFailures
) {
stoppedEarly.push(
logger.yellow(
`${ident(baseIdent)}Testing stopped early after ${
this.pwConfig.maxFailures
} maximum allowed failures`
)
);
}
Something similar should be possible for failOnFlakyTests
Motivation
Improve reporter output abilities
🚀 Feature Request
Move failOnFlakyTests from the internal config to the public config so reporters that take over stdout can reason about why the run failed in the output.
Similar to maxFailures.
Example
Similar to maxFailures, reporters that print to stdout should be able to reason about why a run failed in their onEnd.
Here is an example printer snippet that uses maxFailures:
Something similar should be possible for failOnFlakyTests
Motivation
Improve reporter output abilities