Skip to content

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

@twk3

Description

@twk3

🚀 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions