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
It is pretty difficult to figure out what goes wrong when no information is given about which test fails.
Here is an example:
[ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 62.605 s <<< FAILURE! - in org.intocps.maestro.FullSpecCppTest
[ERROR] org.intocps.maestro.FullSpecCppTest.test(String, File)[1] Time elapsed: 0.817 s <<< FAILURE!
org.opentest4j.AssertionFailedError: The sha1 of the generated spec and the sim program did not match. ==> expected: <true> but was: <false>
at org.intocps.maestro.FullSpecCppTest.postProcessSpec(FullSpecCppTest.java:107)
its a version of the FullSpecTest test so it has 9 sub tests. so while it can run them it is not useful if it doesn't show information about which ones fails.
The text was updated successfully, but these errors were encountered:
Yes that sucks.
We were unaware of this... But apparently it is surefire that seems to be behind, not junit5
Should work with surefire 3.0.0-M5 though?!
Why did we switch to Junit 5 when it doesn't support the test structure we have with parametric tests?
junit-team/junit5#990
It is pretty difficult to figure out what goes wrong when no information is given about which test fails.
Here is an example:
its a version of the
FullSpecTest
test so it has 9 sub tests. so while it can run them it is not useful if it doesn't show information about which ones fails.The text was updated successfully, but these errors were encountered: