| Buckminster reporting skipped tests as failures? [message #1238409] |
Sat, 01 February 2014 08:27 |
 Volker Stolz
Messages: 63
Registered: July 2009 |
Member |
|
|
I have a few unit tests using JUnit's Assume.assumeTrue() that skip the tests e.g. on machines where necessary software is not available. Within Eclipse, these tests are correctly reported as skipped (not failed). The log-file produced by innovating Bucky's (4.3) "emma" (I'm also recording coverage with Jacoco) though on Jenkins shows:
<failure>org.junit.internal.AssumptionViolatedException: MY_CUSTOM_MESSAGE_HERE
at org.junit.Assume.assumeTrue(Assume.java:59)
at deadlock.DeadlockCheckerTests.onError(DeadlockCheckerTests.java:21)
at abs.frontend.typesystem.ExamplesTypeChecking.parse(ExamplesTypeChecking.java:37)
at deadlock.DeadlockCheckerTests.parse(DeadlockCheckerTests.java:26)
at abs.frontend.parser.ParseSamplesTest.test(ParseSamplesTest.java:54)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
and thus Jenkins reports them as failed. Is this expected? The mailing lists seems to indicate that at least via ANT or Maven skipped tests are accounted correctly in Jenkins.
|
|
|
Powered by
FUDForum. Page generated in 0.03915 seconds
] 
Search
Help
Register
Login
Home
