Hi, On Fri, Mar 11, 2016 at 1:46 PM, Stefan Egli <[email protected]> wrote: > ...But short term, I think we could exclude them and put them in a separate > integration tests category...
As I said I don't want to exclude all integration tests by default, we need to be more granular. A cheap way of marking those tests as slow is to move them so that their Java package name includes the word "slow" with dots around it. We can then configure the testing plugins to ignore such tests by default, this should work regardless of which version of JUnit or the plugins is used (to be verified). That's assuming those tests work if moved to different packages, otherwise we might define a class naming convention like FooTestSlow and FooITSlow instead, but that's a bit uglier. > ...renaming them to IT > excludes them from 'mvn test' but also from 'mvn verify' it seems.. That's probably due to an incomplete or incorrect maven-failsafe-plugin configuration. That config is correct in the testing/samples/bundle-with-it module, for example. -Bertrand
