Ability to Rerun only failing specs of previous execution

[SwardCoder]

What would you like?

Providing the Ability of Rerun to only Failing test cases of Previous Execution will help us a
as doing it manually will be time time-consuming process as we need to collect names/paths of failing specs and we should be able to run them manually by using --spec command

at least if this facility is provided in paid subscriptions it will be more useful in saving infrastructure costs to run test cases

We have a situation to run 500 specs and it takes around 4 hrs to complete when using 6 VMs in Archestrization finally if we find any failing test cases (which are not flaky test failures) for example 50
then we will ask Developers to fix them and then instead of spending 4 hours again we will run only these 50 instead,

if Cypress provides this facility by saving the details of failing specs in Memory and upon second execution if it prompts do you want to run only failures of the previous run and if it Executes it helps us

Maybe it's not in the scope of Cypress Cloud but yes it can send some output kind of thing to CI/CD surely this kind of feature will help us

Why is this needed?

No response

Other

No response

[ryanpei]

@SwardCoder which CI are you using?

Also, please look into Spec Prioritization and Auto Cancellation. Used together, they ensure that, on the next run, the failed specs will run first and then, depending on your Auto Cancellation threshold, the run stops after X failures. This way, you can ensure that you're only going to see the whole test suite run again once the failures are fixed. And you do want to make sure no other tests were failed because of the "fix", so it's recommended to re-run everything at the end anyway.

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.