[Feature]: Retry Mechanism for Failed Scenarios:

[Rahimtulla]

🚀 Feature Request

Introduce a dedicated retry mechanism specifically for re-executing failed scenarios. This feature would enable teams to quickly validate intermittent failures without rerunning the entire test suite, saving time and resources during CI/CD processes.

Example

No response

Motivation

In large-scale test automation, intermittent failures can occur due to transient issues such as environmental instability, network delays, or temporary system unavailability. Addressing these failures often involves rerunning the entire test suite, which is time-consuming and inefficient, especially in CI/CD pipelines where quick feedback is crucial.

A dedicated retry mechanism for re-executing only failed scenarios would provide a more efficient approach to managing these intermittent issues. By isolating and retrying the failed scenarios, teams can quickly validate whether the failures are genuine or transient, without expending unnecessary time and resources on rerunning successful tests.

This feature would significantly enhance the efficiency of CI/CD workflows, reduce the turnaround time for test executions, and allow teams to focus on resolving real issues rather than debugging flaky or transient failures.

[Az8th]

Have you already tried using npx playwright test --last-failed ?