[Feature] Add Retries

[mxschmitt]

Retries got reverted since there were bugs in it which would prevent users from using it efficiently.

Open items:

• Make sure it works with timeouts
• Make sure SetUp and TearDown runs as expected
• Add more tests for edge cases
• Revert chore: make retry attributes internal #2315
• Revert microsoft/playwright@59c32bf

[bheemreddy181]

Really looking forward into this - we are missing retries at this moment

[bheemreddy181]

Can we also make retries differ based on the tag - like say if we have API tests then set retries to 0 and set retries to number n for web tests ?

[mxschmitt]

Retries would be for the whole project, so you can define <Retries>1</Retries> inside your runsettings file or when defining it via --settings to dotnet test. This is the same way how it's done for Node.js.

Just a question out of curiosity, are you using NUnit or MSTest?

[bheemreddy181]

We are using Nunit - makes sense you can ignore the tag request. It’s better to have different run settings for different tag runs

[nicolaiarocci]

Looking forward to this one too.

[masaplecas]

Is there any ETA about this one?

[DavinderZilo]

Any update on this, it will really help where tests at times fail duty flakey backend

[ArcadeMode]

Is there any news on this? We're enjoying using playwright-dotnet a lot but retries would save us a lot of effort on manually re-running tests that fail due to random failures.

[autom3tion]

Really would appreciate if we'd get some info on this. I see PlaywrightSettingsProvider has Retries option, but it doesn't work.

[TheJackGower]

Is there an ETA yet? Would be a great feature to have.

[gauravkhuraana]

Dotnet is lagging compared to nodejs in many perspective. Can we please bring it to speed and bring on these features

[ashleybissell]

Do we have any timescales for when this might be looked at again? It appears to be a popular issue and would be a big help to a lot of users.

[ertiusmeo]

Is there any plan for this feature? It would be nice to have it.

[mxschmitt]

@ertiusmeo we are actively exploring options for NUnit and MSTest and collaborate with the MSTest maintainers. (no eta unfortunately)