maestro icon indicating copy to clipboard operation
maestro copied to clipboard

Juni5 not supporting parametric tests

Open lausdahl opened this issue 3 years ago • 1 comments

Why did we switch to Junit 5 when it doesn't support the test structure we have with parametric tests?

https://github.com/junit-team/junit5/issues/990

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.

lausdahl avatar Jul 20 '21 11:07 lausdahl

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?!

CThuleHansen avatar Aug 02 '21 11:08 CThuleHansen