On Sun, Nov 6, 2016 at 8:48 AM Kevin Burton wrote:
> > If you like to parallize the unit tests themself you have to configure
> > maven-surefire-plugin accordingly...I recommend reading the doc about
> that
> > subject[2].
>
> Ah.. interesting. Those changes should be incorporated back into maven
>
>
> Is this really the time for the tests only or is this the whole build time
> including the test time? If it is only the time for running the tests it
> means those tests are slow...
>
>
Yeah. I agree. The slow ones are all essentially integration tests.
Some take 20-30 seconds as they invo
>
>
> I'm thinking of a clunky approach of including tests with names starting
> with [A-Ma-m] in one build configuration, and those with names starting
> with [^A-Ma-m] in another build configuration. These build configuration
> could have most of their actual configuration in a build template, an
Hi Kevin,
On 05/11/16 22:33, Kevin Burton wrote:
We use TeamCity internally (which is great btw) for Maven testing.
We have about 2000 tests which we continually integrate on every commit.
The problem is that testing takes about 15 minutes from start to end.
Is this really the time for the t
Apparently "includes" support fairly complex syntax, such as regexes:
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#includes
I'm thinking of a clunky approach of including tests with names starting with
[A-Ma-m] in one build configuration, and those with names starting wi
