You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that writing tests is rather unnatural compared to, for instance, the core API's "failBecauseExc..." Argh, can't say it. shouldHaveThrown().
Since it throws an AssertionError, if we write, in a test:
(and find a shorter name for it?)
The problem is that writing tests is rather unnatural compared to, for instance, the core API's
"failBecauseExc..."
Argh, can't say it.shouldHaveThrown()
.Since it throws an
AssertionError
, if we write, in a test:even though the naturally expected result that the verification code was not hit, it is.
Instead one has to write this rather unwieldy code:
Why not make it throw a custom
AssertionErrorExpectedException
instead?Also, why not an alternate name of
wasExpectingAssertionError()
?The text was updated successfully, but these errors were encountered: