Open mxschmitt opened 2 years ago
Really looking forward into this - we are missing retries at this moment
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 ?
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?
We are using Nunit - makes sense you can ignore the tag request. It’s better to have different run settings for different tag runs
Looking forward to this one too.
Is there any ETA about this one?
Any update on this, it will really help where tests at times fail duty flakey backend
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.
Really would appreciate if we'd get some info on this. I see PlaywrightSettingsProvider
has Retries
option, but it doesn't work.
Is there an ETA yet? Would be a great feature to have.
Dotnet is lagging compared to nodejs in many perspective. Can we please bring it to speed and bring on these features
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.
Is there any plan for this feature? It would be nice to have it.
@ertiusmeo we are actively exploring options for NUnit and MSTest and collaborate with the MSTest maintainers. (no eta unfortunately)
Retries got reverted since there were bugs in it which would prevent users from using it efficiently.
Open items: