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
Currently, it always throws AssertionError. But if there's only one failure and it's a ComparisonFailure, we should throw ComparisonFailure. Arguably we could throw ComparisonFailure even in the case of multiple failures, at least if only one input is a ComparisonFailure, though that's potentially confusing.
The text was updated successfully, but these errors were encountered:
Arguably we could throw ComparisonFailure even in the case of multiple failures, at least if only one input is a ComparisonFailure, though that's potentially confusing.
There's also a MultipleFailuresException in JUnit 4. But it looks like that might be less supported by IDEs than MultipleFailuresError (which itself might not be heavily supported).
Currently, it always throws
AssertionError
. But if there's only one failure and it's aComparisonFailure
, we should throwComparisonFailure
. Arguably we could throwComparisonFailure
even in the case of multiple failures, at least if only one input is aComparisonFailure
, though that's potentially confusing.The text was updated successfully, but these errors were encountered: