On 12/01/07, Terry C Martin [EMAIL PROTECTED] wrote:
I have an application in which I make use of AspectJ Load-time-weaving to
inject pojos with services from Spring. I have some integration tests which
test that the pojo is able to be injected and collaborate with the injected
service
Hi,
i have problems integrating Cargo Deployment and Surefire Tests. I've bound
cargo:start to pre-integration-test, surefire:test to integration-tests and
finally cargo:stop to post-integration-test.
The problem is that surefire executes twice. Once in test:test and once in
integration-test
Allright - that worked! Thanks a bunch!
--
View this message in context:
http://www.nabble.com/Surefire%2C-Cargo-and-Integration-Tests-tf3117463s177.html#a8637699
Sent from the Maven - Users mailing list archive at Nabble.com
See http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
On 1/25/07, takai [EMAIL PROTECTED] wrote:
Hi,
i have problems integrating Cargo Deployment and Surefire Tests. I've bound
cargo:start to pre-integration-test, surefire:test to integration-tests and
finally
Hi,
Take a look at this:
http://docs.codehaus.org/pages/viewpage.action?pageId=62120
Bashar
-Original Message-
From: takai [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 25, 2007 9:47 AM
To: users@maven.apache.org
Subject: Surefire, Cargo and Integration Tests
Hi,
i have
I have an application in which I make use of AspectJ Load-time-weaving to
inject pojos with services from Spring. I have some integration tests which
test that the pojo is able to be injected and collaborate with the injected
service successfully. These tests run successfully within Eclipse's
the test phase, or the integration-test
phase.
Btw, there are no default goals for the integration-test ( see [1] ), and
there are no default directories for the integration test files ( see [2] ).
As to how integration tests are usually done by maven, there's usually
another maven project just
directories for the integration test files ( see [2] ).
As to how integration tests are usually done by maven, there's usually
another maven project just for the integration testing.
Cheers,
Franz
[1] http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle
[2] http
integration tests running?
Thanks,
Todd
There are various integration tests run as part of the Maven project
build itself, which of course uses Maven to do the build and test etc.
I'd take a look at their poms and how they've structured the
integration test directories etc to see how you might be able to apply
it to your own project
or
to add your integration source as part of /src/test/java and
/src/test/resources.
ciao
Derek
Wayne Fay wrote:
There are various integration tests run as part of the Maven project
build itself, which of course uses Maven to do the build and test etc.
I'd take a look at their poms and how
Wayne Fay wrote:
There are various integration tests run as part of the Maven project
build itself, which of course uses Maven to do the build and test etc.
I'd take a look at their poms and how they've structured the
integration test directories etc to see how you might be able to apply
at an answer would dbe to either create
subprojects or
to add your integration source as part of /src/test/java and
/src/test/resources.
ciao
Derek
Wayne Fay wrote:
There are various integration tests run as part of the Maven project
build itself, which of course uses Maven to do the build
Hi,
I would like to run both unit tests and integration tests in the same project.
I don't want to create a separate module for integration tests (unlike Better
Builds With Maven book).
With only one project (and one pom), I want the following lifecycle:
Phase |Action
On 27/11/06, Julien HENRY [EMAIL PROTECTED] wrote:
I would like to run both unit tests and integration tests in the same project.
I don't want to create a separate module for integration tests (unlike Better
Builds With Maven book).
You can achieve this, but it's not too pretty. See:
http
OK, so I'll have to wait for Maven 2.1 ;)
Thanks
- Message d'origine
De : Mark Hobson [EMAIL PROTECTED]
À : Maven Users List users@maven.apache.org
Envoyé le : Lundi, 27 Novembre 2006, 10h33mn 07s
Objet : Re: Running both unit and integration tests in the same module
On 27/11/06
Hi,
I have a slightly unusual situation where I have shared overlay webapps
that are assembled into standalone webapps and into larger aggregate
webapps. The httpunit (junit) integration tests are contained within
the overlay (component) project. However, I'd like to execute the same
]
Sent: Monday, November 27, 2006 8:47 PM
To: Maven Users
Subject: executing junit (integration) tests against a different project
Hi,
I have a slightly unusual situation where I have shared overlay webapps
that are assembled into standalone webapps and into larger aggregate
webapps
PROTECTED]
Sent: Monday, November 27, 2006 8:47 PM
To: Maven Users
Subject: executing junit (integration) tests against a different project
Hi,
I have a slightly unusual situation where I have shared overlay webapps
that are assembled into standalone webapps and into larger aggregate
webapps
(integration) tests against a different
project
Hi Nir,
yes I was thinking that, but then there's a problem if the aggregator
project has tests of its own, or if the aggregator project aggregates
more than one overlay webapp.
I'm thinking copying all test sources into a single folder may be the
only
in the integration-test
phase. These are all in in the .../integration/.. package
I have the following in my pom, but the plugin still insists on running
the integration tests in the test phase.
What is wrong with this configuration ?
plugin
artifactIdmaven-surefire-plugin/artifactId
On 10/12/06, Jan-Olav Eide [EMAIL PROTECTED] wrote:
I have a set of tests that I only want to run in the integration-test
phase. These are all in in the .../integration/.. package
I have the following in my pom, but the plugin still insists on running
the integration tests in the test phase
I have a set of tests that I only want to run in the integration-test
phase. These are all in in the .../integration/.. package
I have the following in my pom, but the plugin still insists on running
the integration tests in the test phase.
What is wrong with this configuration ?
plugin
can test it in clustered mode.
3. How do I lay out my projects for integration testing? I have 3 projects.
messageDrivenPojo
messageDrivenDelegate
messageDrivenSender
I need to integration test both messageDrivenSender and
messageDrivenDelegate. Message driven delegate integration tests should
structure do I lay out, do I use the following?
src/integration-tests/java
src/integration-test/resources
I'm not clear on how to include this as a project, but exclude the tests
from the unit tests, and only run them during the integration tests, and I
can't find any documentation on it.
You can only
that contains all the jars and the class path for the executable jar. Is it
possible for me to automatically run the assembly and upload the created zip
during release:perform?
2. I have a project that has both unit tests and integration tests. The
unit tests use mock objects and obviously
and integration tests. The
unit tests use mock objects and obviously execute automatically when test is
performed. How do I specify the tests that need to run for integration
testing? Also note that I will need to start Jboss in the
pre-integration-test phase and shut it down in the post
On 8/30/06, Todd Nine [EMAIL PROTECTED] wrote:
2. I have a project that has both unit tests and integration tests. The
unit tests use mock objects and obviously execute automatically when test is
performed. How do I specify the tests that need to run for integration
testing? Also note that I
in
surefire (or in cargo)?
NOTE: Both are using the same jdk + junit version.
Tony.
--
View this message in context:
http://www.nabble.com/-m2--surefire-and-integration-tests---discrepancy-tf2138839.html#a5902585
Sent from the Maven - Users forum at Nabble.com
[mailto:[EMAIL PROTECTED]
Sent: lundi 21 août 2006 09:53
To: users@maven.apache.org
Subject: [m2] surefire and integration tests - discrepancy
Hi all,
I am currently running functional tests with surefire + cargo and IntelliJ
IDEA. I have set both to the same container (tomcat5).
When
:[EMAIL PROTECTED]
Sent: lundi 21 août 2006 09:53
To: users@maven.apache.org
Subject: [m2] surefire and integration tests - discrepancy
Hi all,
I am currently running functional tests with surefire + cargo and
IntelliJ
IDEA. I have set both to the same container (tomcat5).
When
setting the basedir environment variable to the same
location in IDEA as it's set up in Maven2?
-Vincent
-Original Message-
From: Tony Truong [mailto:[EMAIL PROTECTED]
Sent: lundi 21 août 2006 10:15
To: users@maven.apache.org
Subject: RE: [m2] surefire and integration tests - discrepancy
Ok, looks like I found the problem - when using -javaagent option,
all agent dependencies have to be passed as -bootclasspath in
argLine/. I'll see if I can decouple the agent from the rest of the
framework. In the meantime, is there a Maven environment variable
that I can reference in the
Hi,
I'm trying to write a maven2 pom.xml for commons-logging. Running the
unit tests is a little tricky, because there are lots of tests that
explicitly configure their own classpath, using the artifacts created
during the build process.
I've therefore got a set of unit tests that run in the
Sorry, please ignore previous email. The problem is that my unit test is
explicitly looking for junit via the system classloader. Of course
surefire is loading junit via a custom classloader.
Regards,
Simon
On Tue, 2006-07-25 at 10:34 +1200, Simon Kitching wrote:
Hi,
I'm trying to write a
Can anyone point me to any documentation on the maven-it-plugin?
I expect I've missed something but
- I can't find the plugin documentation at maven.apache.org
- there is very little in the mail archives about it
- googling hasn't really helped find the scm for the plugin either...
From my
- googling hasn't really helped find the scm for the plugin either...
I'm blind.
It's available at
http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 6/12/06, Jeremy Whitlock [EMAIL PROTECTED] wrote:
I would like to know the proper way to run in-container integration/unit
tests for applications built/tested using Maven. I have tried to run
jetty6:run before the test phase but it does not start as a daemon or forked
so Maven never
Wendy,
How funny to run into you. I read some of your stuff earlier thanks to
Google. I was going to do the same thing by requiring Jetty for the test
phase and having an extendable test who's setUp() method would embed a Jetty
instance then deploy the webapp. I didn't look too far into it
Hi Jeremy,
Have you read Better builds with Maven
(http://www.mergere.com/m2book_download.jsp)?
In chapter 4.13 (Testing J2EE Applications) there's an instruction on how to
start a container (Geronimo in that case) with Cargo in the pre-integration
phase and to stop it in the post-integration
Hi all,
I would like to know the proper way to run in-container integration/unit
tests for applications built/tested using Maven. I have tried to run
jetty6:run before the test phase but it does not start as a daemon or forked
so Maven never continues to finish running the rest of the
test case.)
I do keep integration tests in a separate module for my production
apps, but the use case here is a simple 'blank' app (or an archetype)
that someone can quickly understand and get up to speed for
development and testing. (See MNG-2344.)
--
Wendy
To: Maven Users List
Subject: [m2] Unit tests and integration tests in the same module?
[moved from [EMAIL PROTECTED]
Context: We want to run both 'normal' unit tests, and integration
tests that require a webapp to be deployed in a container, from the
same module.
On 6/5/06, Brett Porter [EMAIL
On 6/7/06, Vincent Massol [EMAIL PROTECTED] wrote:
I don't believe it's currently possible within the same build module.
We started discussing it on
http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+strategies
What about:
* src/itest instead of src/it
*
Users List'
Subject: RE: [m2] Unit tests and integration tests in the same module?
I don't believe it's currently possible within the same build module.
We started discussing it on
http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+strategies
-Vincent
-Original Message-
From
Users List
Subject: RE: [m2] Unit tests and integration tests in the same module?
I was able to do by using testng and not providing a testng.xml file for the
test phase, but only for the integration-test phase. It is kinda of a hack,
but it works.
-Original Message-
From: Vincent Massol
[moved from [EMAIL PROTECTED]
Context: We want to run both 'normal' unit tests, and integration
tests that require a webapp to be deployed in a container, from the
same module.
On 6/5/06, Brett Porter [EMAIL PROTECTED] wrote:
It *should* still be possible to achieve what you want currently (I
: Wednesday, May 03, 2006 3:58 PM
To: Maven users list
Subject: [m2] code coverage for multiple modules that use integration
tests
Okay, I have a number of modules and I want to generate code coverage
for them with cobertura. Some of the classes can be tested with normal
unit tests so
Okay, I have a number of modules and I want to generate code coverage
for them with cobertura. Some of the classes can be tested with normal
unit tests so they are not a problem. Some of the classes, however, are
Tapestry components. To test them I have a separate module called
integration-tests
for multiple modules that use integration
tests
Okay, I have a number of modules and I want to generate code coverage
for them with cobertura. Some of the classes can be tested with normal
unit tests so they are not a problem. Some of the classes, however, are
Tapestry components. To test them I
Hi James,
I did indeed, for me the problem was with the path to where m2 was installed
on windows. It took me a while to find it but this is a known bug in the jdk
when invoking an RMI server from a directory with spaces in the path..
So to get around it I moved m2 from c:\program
[EMAIL PROTECTED] wrote:
Back on Feb 11 there was a thread regarding
integration testing with the subject line How to bind
execution of integration tests to integration-test
phase.
Like Pete, who offered good advice in that thread, I
also need to do in-container testing via Cactus, run
Back on Feb 11 there was a thread regarding
integration testing with the subject line How to bind
execution of integration tests to integration-test
phase.
Like Pete, who offered good advice in that thread, I
also need to do in-container testing via Cactus, run
CruiseControl and deploy to OAS
execution of integration tests to integration-
test phase
I have achieved integration testing (both JunitEE/Cactus and JUnits
calling
remote interfaces) in M2 using a very simple lightweight POM for each
discrete task/execution in the integration phase e.g.
+ runtests-integration
pom.xml
Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: dimanche 12 février 2006 10:53
To: 'Maven Users List'
Subject: RE: How to bind execution of integration tests to integration-
test phase
Hi Pete,
Yes, you've found the only possible way as of now to perform integration
to Ant Plugins.
I'm hoping that when M2 supports integration tests more I can migrate to the
approved strategy, but this works right now, we have Applications (both
EARs) that are built with M2 via CruiseControl, the above integration
projects start the container run all the integration tests
Hi
I have a set of JUnit unit tests which are executed during the test
lifecycle phase.
Now I want to add integration-test classes in another directory to be
executed during the integration-test phase.
How do I accomplish that?
Using Maven2 and ANT.
Regards,
/B-E
Hi,
-Original Message-
From: Bengt-Erik Fröberg [mailto:[EMAIL PROTECTED]
Sent: mardi 10 janvier 2006 14:34
To: 'Maven Users List'
Subject: How to bind execution of integration tests to integration-test
phase
Hi
I have a set of JUnit unit tests which are executed during
of integration tests to integration-test
phase
Hi,
-Original Message-
From: Bengt-Erik Fröberg [mailto:[EMAIL PROTECTED]
Sent: mardi 10 janvier 2006 14:34
To: 'Maven Users List'
Subject: How to bind execution of integration tests to integration-test
phase
Hi
I have a set
-Original Message-
From: Bengt-Erik Fröberg [mailto:[EMAIL PROTECTED]
Sent: mardi 10 janvier 2006 16:28
To: 'Maven Users List'
Subject: SV: How to bind execution of integration tests to integration-
test phase
Hi and thanks for answering.
I see but what does
of integration tests to integration-test
phase
-Original Message-
From: Bengt-Erik Fröberg [mailto:[EMAIL PROTECTED]
Sent: mardi 10 janvier 2006 16:28
To: 'Maven Users List'
Subject: SV: How to bind execution of integration tests to integration-
test phase
Hi and thanks for answering
Hi,
I was just wondering where I should put my integration tests if I want to
keep them separate from my unit tests wich are of course under
/src/test/java. Any idea?
Thank!
--
Alexandre Poitras
Québec, Canada
-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
Sent: mardi 10 janvier 2006 21:12
To: Maven Users List
Subject: [M2] Integration tests location
Hi,
I was just wondering where I should put my integration tests if I want to
keep them separate from my unit
:
https://svn.apache.org/repos/asf/maven/plugins/trunk
Jochen Wiedmann wrote:
Hi,
can anyone point me to a plugin with included integration tests, that
I may use as an example? Preferrably, a source generating plugin?
All plugins that I know so far, have either a simple test directory
Hi,
can anyone point me to a plugin with included integration tests, that I
may use as an example? Preferrably, a source generating plugin?
All plugins that I know so far, have either a simple test directory,
or no tests at all.
Regards,
Jochen
: [M2] Any guides or recommendations for Cactus / JUnitEE /
Integration Tests
I've reached the stage where I want to be able to run some JUnits that
require :-
- Incontainer JUnits (to be run by JUnitEE or Cactus)
- JUnits that call Session Beans (therefore J2EE container needs
I'm using Maven 1.1 right now, and I'd like to separate my JUnit unit
tests from my JUnit integration tests. The former test only a single
class/layer of the app, while the latter test from the service layer
to the database. I'm using Spring and JDO2, and the app is a web
services app. I
Whoops, sorry. I'm using Maven 1.0.2 actually.
Mark
On Sep 17, 2005, at 11:51 AM, Mark Slater wrote:
I'm using Maven 1.1 right now, and I'd like to separate my JUnit
unit tests from my JUnit integration tests. The former test only a
single class/layer of the app, while the latter test from
You could create another project that holds only your integration tests.
Cheers,
Thomas
On 9/17/05, Mark Slater [EMAIL PROTECTED] wrote:
Whoops, sorry. I'm using Maven 1.0.2 actually.
Mark
On Sep 17, 2005, at 11:51 AM, Mark Slater wrote:
I'm using Maven 1.1 right now, and I'd like
them
more closely associated with the project it's testing, but could do it
as a last resort.
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 10:56 AM
To: 'Maven Users List'
Subject: RE: Running integration tests
-Original Message
For one of my projects, I need to add some integration tests that are
separate from the unit tests. The unit tests work as they should--they
are fully automated and run with every build. The integration tests are
different in that they can't be fully automated since they depend on
some external
-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED]
Sent: vendredi 13 mai 2005 18:32
To: Maven Users List
Subject: Running integration tests
For one of my projects, I need to add some integration tests that are
separate from the unit tests. The unit tests work
-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED]
Sent: vendredi 13 mai 2005 18:32
To: Maven Users List
Subject: Running integration tests
For one of my projects, I need to add some integration tests that are
separate from the unit tests. The unit tests work
tests
For one of my projects, I need to add some integration tests that are
separate from the unit tests. The unit tests work as they should--they
are fully automated and run with every build. The integration tests are
different in that they can't be fully automated since they depend
-Original Message-
From: Thomas Van de Velde [mailto:[EMAIL PROTECTED]
Sent: vendredi 13 mai 2005 20:01
To: Maven Users List
Subject: Re: Running integration tests
Vincent,
Any plans on building Cargo support for WAS?
Definitely... as soon as someone is interested
-Original Message-
From: Thomas Van de Velde [mailto:[EMAIL PROTECTED]
Sent: vendredi 13 mai 2005 20:01
To: Maven Users List
Subject: Re: Running integration tests
Vincent,
Any plans on building Cargo support for WAS?
Definitely... as soon as someone is interested
Hi,
I'm a newbie to Maven, and trying to set up our project to run both
integration tests and unit tests.
The unit tests are fine - just specified the directory under the
unitTestSourceDirectory tag.
However, we have integration tests that reside in a sister directory ie
test.mypackage.unit
You have two options:
- create your own plugin that runs the unit tests from the second directory
- separate the integration tests out into a separate project, and run
them using the completed JAR from the other project
If the integration tests run under different conditions, they are
generally
Thanks Dan.
I set up a separate project as you suggested, which includes a
dependency on the main project.
This works fine, but it requires me to jar:install my main project each
time I run the integration tests.
So I'd like to make the integration tests a subproject and add a
dependency
:
Thanks Dan.
I set up a separate project as you suggested, which includes a
dependency on the main project.
This works fine, but it requires me to jar:install my main project each
time I run the integration tests.
So I'd like to make the integration tests a subproject and add a
dependency
stay in the main source directory.
(not the unit test src)
After that, use jelly/java to drive your integration in maven.xml
-D
On Wed, 2 Mar 2005 17:42:31 +0100, Ralph Pöllath [EMAIL PROTECTED]
wrote:
Hi,
In addition to my unit tests, I have some integration tests which I'd
like to be able to run
Hi,
In addition to my unit tests, I have some integration tests which I'd
like to be able to run separately (they require a database to be
available, etc).
What's the preferred way to do this with maven?
Thanks,
-Ralph
PROTECTED] wrote:
Hi,
In addition to my unit tests, I have some integration tests which I'd
like to be able to run separately (they require a database to be
available, etc).
What's the preferred way to do this with maven?
Thanks,
-Ralph
-Original Message-
From: Tim Stephenson [mailto:[EMAIL PROTECTED]
Sent: Monday, April 26, 2004 1:29 PM
To: '[EMAIL PROTECTED]'
Subject: Query on current approach to integration tests
Hi,
I notice that there have been a few changes to the project xsd (and
supporting
tests ( basically how we are doing it in ant now ).
I like the idea of having a separate project, especially for
acceptance/functional testing. The other thing that the pain of
separating what you define ( and myself btw ) as integration tests in
maven provides is motivation for not writing slow
Hi,
I'm working on a webapp where I've got a bunch of domain model unit
tests in src/test and then want to put some HttpUnit integration
tests in something like src/iu-test or src/web-test.
I was hoping to use the pom's integrationUnitTestDirectory element,
but it seems to be no longer used
201 - 286 of 286 matches
Mail list logo
