Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Make it possible to set up 'maxFailures' within the project in the config file #33665

Open
dmrock opened this issue Nov 19, 2024 · 0 comments
Labels
feature-test-runner Playwright test specific issues P3-collecting-feedback

Comments

@dmrock
Copy link

dmrock commented Nov 19, 2024

🚀 Feature Request

Make it possible to set up 'maxFailures' within the project in the config file

Here is an example:
{ name: 'setup', testMatch: /.*\.setup\.ts/, testDir: './tests', maxFailures: 2 },

Example

This setting will allow us to avoid running, for example, all the authorization tests in the setup file used as a dependency for the main project tests.

When this can be useful:

For instance, before testing, we perform 20 authorizations for different user types in a single application. The authorization goes through the UI, and there’s a bug in the UI. If the very first authorization test fails, the main project tests won’t be executed, but the remaining 19 authorization tests will still run, which, considering retries, will take a significant amount of time.

Motivation

It would be much more efficient to stop the execution after the first failure and analyze it as quickly as possible. This is especially important on the CI.

@dgozman dgozman added feature-test-runner Playwright test specific issues P3-collecting-feedback labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-test-runner Playwright test specific issues P3-collecting-feedback
Projects
None yet
Development

No branches or pull requests

2 participants