Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.8.1
-
None
Description
It seems strange to me to not return "0 Error(s): ()" in the now RuntimeException but soon to be AssertionError when the output is correctly matched but in the incorrect order