Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Buckminster reporting skipped tests as failures?
Buckminster reporting skipped tests as failures? [message #1238409] Sat, 01 February 2014 08:27
Volker Stolz is currently offline Volker StolzFriend
Messages: 63
Registered: July 2009
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(
	at deadlock.DeadlockCheckerTests.onError(
	at abs.frontend.typesystem.ExamplesTypeChecking.parse(
	at deadlock.DeadlockCheckerTests.parse(
	at abs.frontend.parser.ParseSamplesTest.test(
	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(

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.
Previous Topic:Cross-platform builds with buckminster 4.3
Next Topic:Bundle .... cannot be resolved. Why?
Goto Forum:

Current Time: Mon Jul 15 00:22:51 GMT 2024

Powered by FUDForum. Page generated in 0.03159 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top