Hello,
BTW: you should put src/integration-test/java in testSourceDirectory
or you use src/test/java, so all other things follow automatically.
Gruss
Bernd
Am Thu,
01 Jan 2015 17:50:26 -0600 schrieb Ole Ersoy ole.er...@gmail.com:
Hi,
Trying to get some integration tests running. I've
And put your integration tests in another module, that way it can depend
upon the completed results of what you want to integrate and you wont have
to muck around with separating your unit tests from it (since you will
*only* have integration tests in this module)
On 2 January 2015 at 13:55,
Hello,
Me again - Just ignore this post. Just realized that run the integration tests
I can't just do:
mvn clean test
But must do
mvn clean verify
Cheers,
- Ole
On 01/01/2015 05:50 PM, Ole Ersoy wrote:
Hi,
Trying to get some integration tests running. I've tried to minimize my pom,
Hi,
Trying to get some integration tests running. I've tried to minimize my pom,
such that everything runs. I pasted my directory structure below. The
maven-build-helper-plugin is used to include the integration-test src
directory. From what I understand the maven-failsafe-plugin now
I think that what you actually want is two executions of surefire (or
one of surefire and one of failsafe) with different test name
patterns.
On Thu, Jan 1, 2015 at 2:40 PM, Ole Ersoy ole.er...@gmail.com wrote:
Hi,
I'm attempting to separate my integration and unit tests using profiles and
A much simpler way would be to end your integration tests in IT instead of
Test and then have failsafe run the tests for you. Much less hacky
On 1 January 2015 at 19:40, Ole Ersoy ole.er...@gmail.com wrote:
Hi,
I'm attempting to separate my integration and unit tests using profiles
and the
Hi,
I'm attempting to separate my integration and unit tests using profiles and the
maven build helper plugin. I have unit tests in the standard directory and
integration tests in `src/integration-test/java`. When I run the default
profile, I expect integration tests to be skipped and unit
On Thu, Jan 1, 2015 at 5:29 PM, Ole Ersoy ole.er...@gmail.com wrote:
Had one more question. In the documentation I have read the integration
test directory is usually added in the generate-test-sources phase. So all
tests are visible during the `test` phase, although they would be excluded
Had one more question. In the documentation I have read the integration test
directory is usually added in the generate-test-sources phase. So all tests
are visible during the `test` phase, although they would be excluded by default
if they end in `IT`.
It seems more Logical to add the
Hi Benson,
I got it working now. I wanted to be able to run the build with an integration
test profile that skips running the unit tests:
`mvn clean verify -P integration-test`
Its working now. Thanks,
- Ole
On 01/01/2015 09:25 PM, Benson Margulies wrote:
I think that what you actually
On 01/01/2015 09:26 PM, Benson Margulies wrote:
On Thu, Jan 1, 2015 at 5:29 PM, Ole Ersoy ole.er...@gmail.com wrote:
Had one more question. In the documentation I have read the integration
test directory is usually added in the generate-test-sources phase. So all
tests are visible during the
Hi Barrie,
Good tip - I'll keep it in mind.
Thanks,
- Ole
On 01/01/2015 09:54 PM, Barrie Treloar wrote:
And put your integration tests in another module, that way it can depend
upon the completed results of what you want to integrate and you wont have
to muck around with separating your unit
You can even use your profile still with this way.
You stick the module definition into the profile.
It does mess with releases; either you enable it with the release (in which
case the release may slow down), or you leave it disabled which means that
the version number doesn't get automatically
13 matches
Mail list logo
