Yeah, I think that would be useful to have. An alternative is to use Maven profiles and use conventions like *IntegrationTest or *MapReduceTest as part of the name of the test class.
Users have the option of running only the unit test, MR tests or do a full build by activating a Maven profile. Another benefit of these naming conventions is it integrates nicely in an IDE because with autocompletion and so on you can quickly see what kind of tests are available. The nightly on Jenkins will run a full build. Would it make a difference in test speed if we used MRUnit for some of the tests? Just curious. Frank On Wed, Jul 4, 2012 at 10:24 PM, Dawid Weiss <[email protected]> wrote: >> These aren't going to get fixed; > > I think the idea is to allow long-running tests on build servers where > they don't really annoy people so much and have a quick run for > developers to check before they commit etc. > > Dawid >
