I understand your point, and agree that I might be nice to have a bit more of a standard place for integration tests. However, one point that should be mentioned is that there are frequently multiple levels of integration tests (in container, out of container, ui, etc). Thus it might not be so simple to just have one spot for integration tests.
John Kramer email: [email protected] mobile: 314.435.2370 skype: kramer.mojiva twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech> 0xCAFEBABE00000032 On 9/17/12 9:05 AM, "Clebert Suconic" <[email protected]> wrote: >That's one thing I always thought that maven should have an explicit >spot for integration tests. We also had to create a separate profile. >Having them into a more standard place would make it cleaner IMO. > >That's a feature request I know. But does it make sense? > >Sent from my iPhone > >On Sep 17, 2012, at 5:39 AM, Barrie Treloar <[email protected]> wrote: > >> On Mon, Sep 17, 2012 at 5:26 PM, Kristian Rosenvold >> <[email protected]> wrote: >>> You should probably be looking into parallelizing your tests :) . >> >> Or looking at what your tests are doing. >> 32 minutes sounds like you are doing integration type testing and not >> unit tests. >> >> Pull the integration tests into their own module, which you include >> via a profile (e.g. "its"), and get your continuous integration server >> to run them for you. >> The developers can then forget about them until they get emailed about >> broken builds. >> >> If they really want to run them, they can just include them via -Pits >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
