> -Original Message-
> From: Kevin Burton
> Sent: Tuesday, October 07, 2014 19:28
>
> Right now I have an overlap of unit and integration tests and
> I want to
> tear out my integration tests and keep them separate. This
> way our unit
> tests execute fast and integration testing takes
Hi Kevin,
the best suggestion i can give is simply make a separate module where
the integration tests should be moved to...
This has the advantage having different location for them, cause they
are more than unit tests which is expressed by using a separate module
furthermore you have the
Right now I have an overlap of unit and integration tests and I want to
tear out my integration tests and keep them separate. This way our unit
tests execute fast and integration testing takes a bit longer.
… and now I’m trying to figure out the best strategy for that.
Reading this:
http://docs
Thomas,
There isn't one right answer. Expect to find lots of variants.
I use a naming convention. Unit tests end in plain-old vanilla Test,
and integration tests end in *ITest. I use a wildcard pattern with
Maven to exclude integration tests since they are long-running and
need less execution. I
On Aug 27, 2010, at 6:34 AM, Thomas Sundberg wrote:
> Assume that we are dealing with a multi module build, how would you
> organize the modules? Would you consider adding a separate
> 'integration-test' tree next to main and test?
I set it up like so:
parent module
|-- domain cl
Hi!
This has been discussed previously. But I would like to ask the list
again, how do you separate integrations test from unit tests in a
Maven project?
I define unit tests as being tests that will run in memory and not use
any external resources. Anything external is mocked away. Everything
wil
