Hi, we have the issue, that the build completes successfully if with configuration failures and skipped tests.
This is the output of the test run (buildr clean test):
===============================================
ff-webapp
Total tests run: 55, Failures: 0, Skips: 55
Configuration Failures: 1, Skips: 66
===============================================
Completed in 29.550s
(the shown output is just the summary for the run of one of the
subprojects).
The configuration failure is e.g.
FAILED CONFIGURATION: @BeforeClass setupIntegrationTest
com.google.inject.CreationException: Guice creation errors:
1) A binding to com.proj.core.common.UrlService was already configured at
com.proj.core.backend.CoreBackendModule.configureServices(CoreBackendModule.java:98).
at com.proj.core.domain.CoreDomainModule.configure(CoreDomainModule.java:47)
1 error
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:358)
at
com.google.inject.internal.InjectorBuilder.initializeStatically(InjectorBuilder.java:153)
at
com.google.inject.internal.InjectorBuilder.build(InjectorBuilder.java:106)
at com.google.inject.Guice.createInjector(Guice.java:93)
at com.google.inject.Guice.createInjector(Guice.java:70)
at com.proj.core.IntegrationTest.setupGuice(IntegrationTest.java:84)
at
com.proj.core.IntegrationTest.setupIntegrationTest(IntegrationTest.java:63)
... Removed 22 stack frames
Is it intended, that configuration failures don't break the tests? Btw.,
the test.using :fail_on_failure is left as default...
Thanx && Cheers,
Martin
signature.asc
Description: This is a digitally signed message part
