I am using NUnit to test a large web application with Selenium.
We are depending on a number of exceptions, either custom or provided by Selenium, to fail the tests. NUnit features a Retry attribute, which repeats a failed test, but only on an explicit assertion error.
Is there any way to handle exceptions as failed assertions by default? Wrapping every relevant statement, or every test as a whole in
Assert.That(TestMethodDelegate, Throws.Nothing)
as suggested here would involve a lot of work and additional boilerplate.
I understand this goes against intended behavior, but I need to bend some rules to tame the misguided nightmare that is Selenium testing.