Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 0.8.1
-
Fix Version/s: 0.9.0
-
Labels: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