I remember encountering something similar when I started out using modules.
Basically the error message claiming that class is not found is a bit
misleading because what it really means is "class failed to load". One of
the causes of such failures is improper configuration of one of that class
Can you try running it directly without maven/failsafe
Use
https://maven.apache.org/plugins/maven-dependency-plugin/usage.html#dependency:build-classpath
Delany
On Sun, 31 Jul 2022 at 08:11, Ryan Lubke wrote:
> Hey Folks,
>
> I’ve been looking into this issue for a couple of days now and have
Hey Folks,
I’ve been looking into this issue for a couple of days now and have run out of
ideas.
Maven Version:3.8.5
Maven Failsafe Version: 3.0.0-M7
Java Version:17.0.4
OS: MacOS 12.5/Apple Silicon
The test compiles fine using the
as "named module" and goes a completely
different path inside.
Do you have an idea how I can get my integration-tests to work with failsafe
3.0.0-M5?
Help greatly appreciated,
Chris
behavior, to start and stop the Test Runner only once
> (with this "mvn verify -P itest" command).
>
> itest is the profile that we have in our pom.xml which includes the classes
> that contain integration tests (using maven failsafe plugin)
>
> Here are the
>>> (which is not my desired result).
>>>>
>>>> The IntelliJ second click -> Run all Tests starts it only once. Our Jenkins
>>>> Job is running the tests with "mvn verify -P itest", so my question is how
>>>> can i c
around an hour. This is because this
> > >>> command starts and stops the Spring Test Runner Server on every class
> > >>> (which is not my desired result).
> > >>>
> > >>> The IntelliJ second click -> Run all Tests starts it
ause this
> >>> command starts and stops the Spring Test Runner Server on every class
> >>> (which is not my desired result).
> >>>
> >>> The IntelliJ second click -> Run all Tests starts it only once. Our
> >>> Jenkins
> >>>
with "mvn verify -P itest", so my question is how
>>> can i change this behavior, to start and stop the Test Runner only once
>>> (with this "mvn verify -P itest" command).
>>>
>>> itest is the profile that we have in our pom.xml which includes the
d stop the Test Runner only once
> > (with this "mvn verify -P itest" command).
> >
> > itest is the profile that we have in our pom.xml which includes the classes
> > that contain integration tests (using maven failsafe plugin)
> >
> > Here are the annotat
sts with "mvn verify -P itest", so my question is how
> can i change this behavior, to start and stop the Test Runner only once
> (with this "mvn verify -P itest" command).
>
> itest is the profile that we have in our pom.xml which includes the classes
> that c
ot;, so my question is how
can i change this behavior, to start and stop the Test Runner only once
(with this "mvn verify -P itest" command).
itest is the profile that we have in our pom.xml which includes the classes
that contain integration tests (using maven failsafe plugin)
Here are
[mailto:p...@hammant.org]
Sent: Saturday, October 13, 2018 9:00 AM
To: Maven Users List
Subject: [SUSPICIOUS] Re: [SUSPICIOUS] Re: Running integration tests twice
against different webapp configurations
You're explicitly calling stop() on both Jetty instances ... (pass or fail) and
not just letting it fa
or already started," even with a different
> key and port.
>
> Thanks,
> Scott
>
> -Original Message-
> From: Thomas Broyer [mailto:t.bro...@gmail.com]
> Sent: Friday, October 12, 2018 2:34 AM
> To: Maven Users List
> Subject: [SUSPICIOUS] Re: Running inte
e: Running integration tests twice against different
webapp configurations
Alternatively, if possible, you could possibly run the app with both
configurations in parallel (two executions of jetty-maven-plugin in
pre-integration-test and post-integration-test phase, using different ports),
and run
at builds a webapp and runs integration tests against
> it using the failsafe plugin and the jetty-maven-plugin.
>
> That is, I use the jetty-maven-plugin to start jetty in the
> pre-integration-test phase, run the tests, then shut jetty down in the
> post-integration-test phase.
>
at integration-test phase)
On Fri, Oct 12, 2018 at 8:44 AM Anders Hammar wrote:
> I'd say you need two modules; one for each IT setup. Each module is a Maven
> project and will then run the integration tests. The actual integration
> test code could then be in a third module and you declare a d
I'd say you need two modules; one for each IT setup. Each module is a Maven
project and will then run the integration tests. The actual integration
test code could then be in a third module and you declare a dependency on
that artifact.
/Anders
On Thu, Oct 11, 2018 at 11:21 PM Ellis, Scott
Hi,
I have a project that builds a webapp and runs integration tests against it
using the failsafe plugin and the jetty-maven-plugin.
That is, I use the jetty-maven-plugin to start jetty in the
pre-integration-test phase, run the tests, then shut jetty down in the
post-integration-test phase
> From: Martin Gainty <mgai...@hotmail.com>
> Sent: Tuesday, May 30, 2017 7:08:43 PM
> To: Maven Users List
> Subject: Re: Running integration tests against a signed jar
>
>
>
>
> From: Gary Gregory &
domains on the
server or is this only signing for protecting the archives?
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Martin Gainty <mgai...@hotmail.com>
Sent: Tuesday, May 30, 2017 7:08:43 PM
To: Maven Users List
Subject: Re: Running integration tests a
From: Gary Gregory <garydgreg...@gmail.com>
Sent: Monday, May 29, 2017 5:01 PM
To: Maven Users List
Subject: Running integration tests against a signed jar
Hi All:
I have a POM that builds a signed jar, so far so good. Unit tests run, no
problem.
Hi All:
I have a POM that builds a signed jar, so far so good. Unit tests run, no
problem.
When integration tests run through fail-safe, the build fails all ITs with:
java.lang.ExceptionInInitializerError
Caused by: java.lang.SecurityException: class "com.example.MyClass"'s
signer i
You can do it one build if you just specify two executions for the failsafe
plugin. Then you can configure different system variables for the
executions.
Andreas
Am Samstag, 28. März 2015 schrieb Tecno Brain :
Separate attract build from integration tests.
In the integration test:
-Set up
, but at least it's the same for all tests and can
be reused. The only change between test runs would be a single JVM
parameter which turns security on and off.
Basically, I want to be able to execute the /pre-integration-test -
integration-tests - post-integration-test - verify/ lifecycle phases
multiple
Separate attract build from integration tests.
In the integration test:
-Set up your system (cleanup, install)
- run with the flag disabled
- run again with the flag disabled
I would use Jenkins build steps rather than maven profiles
On Mar 27, 2015 3:15 PM, Stefan stefan.e...@ontotext.com
pom.xml (not
within the module myproject-api-impl/pom.xml).
Martin
Am 13.03.2015 um 09:34 schrieb Sandra Parsick:
I would move the integration tests from myproject-api-impl to the war module
Regards,
Sandra
Am 13.03.2015 um 09:18 schrieb Martin Gütlein:
The failsave integration tests do
The failsave integration tests do not run. They should be applied to the
whole service (war). But they are defined within a module
(myproject-api-impl) and are therefore skipped. I could not figure out
how to configure this.
Martin
Am 13.03.2015 um 09:00 schrieb Hervé BOUTEMY:
sorry, can't
10.03.2015 um 19:59 schrieb Martin Gütlein:
Hi,
I would like to run integration tests on my project, performing and
testing rest-calls to my server.
I have a maven project layout like with modules:
MyProject-api
MyProject-api-impl
MyProject-webapp
MyProject-webapp-exec
I would move the integration tests from myproject-api-impl to the war module
Regards,
Sandra
Am 13.03.2015 um 09:18 schrieb Martin Gütlein:
The failsave integration tests do not run. They should be applied to the
whole service (war). But they are defined within a module
(myproject-api-impl
Anyone?
Where could I get some help on this issue (already tried stackoverflow
as well)?
Martin
Am 10.03.2015 um 19:59 schrieb Martin Gütlein:
Hi,
I would like to run integration tests on my project, performing and
testing rest-calls to my server.
I have a maven project layout like
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
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 want to run more integration tests as my daemons and command line apps
sometimes have bugs that I’d like to catch before a release.
9/10 these are Guice bindings and pretty easy to figure out what’s
happening quickly.
I would like to actually create new processes as a lot of Java code just
/artifactId
version1.0/version
typeear/type
/dependency
Run integration tests.
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-failsafe-plugin/artifactId
version2.17/version
/version
typeear/type
/dependency
Run integration tests.
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-failsafe-plugin/artifactId
version2.17/version
Well the question you really will want to know is:
do I want any other modules to depend on the integration tests being
successful?
If the answer is yes then you will most likely need to deploy something
(packagingpom/packaging) and that may require adding the missing
bindings into the lifecycle
I would try to skip the deploy goal for this particular plugin
see http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
Ah, yes - this is what I needed. So still use jar packaging but skip
the deploy phase.
Rob
:)
Well the question you really will want to know is:
do I want any other modules to depend on the integration tests being
successful?
The Hatter opened his eyes very wide on hearing this; but all he said
was, Why is a mvn like a writing-desk?
If the answer is no then you will just configure
On 9 October 2014 14:01, Robert Mark Bram robertmarkb...@gmail.com wrote:
Well the question you really will want to know is:
do I want any other modules to depend on the integration tests being
successful?
The Hatter opened his eyes very wide on hearing this; but all he said
was, Why
the surefire:test goal to the
test phase, but binds nothing to integration-test - which is why I
need to add the failsafe plugin to my pom.xml. I didn't need to define
a phase for it, because failsafe's default phase is integration-test.
2) Just run integration tests?
I can see that unit tests are all
So failsafe will pickup
ITblahblah.java
BlahblahIT.java
And a third form that I forget
*ITCase.java
http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#includes
/Anders
3) Run integration tests after compile?
The real reason for question 2
:
So failsafe will pickup
ITblahblah.java
BlahblahIT.java
And a third form that I forget
*ITCase.java
http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#includes
/Anders
3) Run integration tests after compile?
The real reason
Hi Robert,
On 10/6/14 11:31 AM, Robert Mark Bram wrote:
Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need to introduce the
maven
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
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
-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 a bit
run integration tests?
I can see that unit tests are all classes with names like *Test.java
and integration tests are all classes with names like IT.java. But mvn
verify and mvn test seem to run all tests (unit and integrations). Is
there a way to run just one or the other?
So, going from
You got it Robert..
Robert Mark Bram wrote on 07.10.2014 19:59:
OK, this was very helpful too. In this case, I am working with a
multi-module project and I decided it was best to add our selenium
tests in a new project to keep them away from other project code. We
have 13 pom.xml files, not
Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need to introduce the
maven-surefire-plugin to my pom.xml for unit tests. Fair enough
On 6 October 2014 10:31, Robert Mark Bram robertmarkb...@gmail.com wrote:
Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need
, 2014 at 2:45 AM, Brendan Miller catph...@catphive.netwrote:
I currently have some testng integration tests in a maven project. This is
causing problems because the tests get picked up and run during the test
phase, rather than the integration-test phase.
How do I cause tests to be run
http://docs.codehaus.org/plugins/servlet/mobile#content/view/63286
On May 15, 2014 10:14 PM, Brendan Miller catph...@catphive.net wrote:
I currently have some testng integration tests in a maven project. This is
causing problems because the tests get picked up and run during the test
phase
I currently have some testng integration tests in a maven project. This is
causing problems because the tests get picked up and run during the test
phase, rather than the integration-test phase.
How do I cause tests to be run in the integration test phase rather than
test? All of my tests
-Psonatype-oss-release -P
user,local-repository
In the output I can see the 'clean' and the 'site' happen, but the
failsafe integration tests do not run. If I do
mvn verify -P run-it
then the integration tests run as normal.
Cheers, Eric
build
pluginManagement
plugins
integration tests do not run. If I do
mvn verify -P run-it
then the integration tests run as normal.
Cheers, Eric
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-failsafe-plugin/artifactId
' and the 'site' happen, but the
failsafe integration tests do not run. If I do
mvn verify -P run-it
then the integration tests run as normal.
Cheers, Eric
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven
the 'clean' and the 'site' happen, but the
failsafe integration tests do not run. If I do
mvn verify -P run-it
then the integration tests run as normal.
Cheers, Eric
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
\release-settings2652114304406041143.xml
clean verify site --no-plugin-updates -Psonatype-oss-release -P
user,local-repository
In the output I can see the 'clean' and the 'site' happen, but the
failsafe integration tests do not run. If I do
mvn verify -P run-it
then the integration tests run
Ahhh, actually adding -P run-it to the preparationGoals parameter does
exactly what I want, and I can dispense with all the other complexities.
I did not realize I could add other arguments to the preparationGoals
parameter.
Sometimes getting what you want from Maven is not obvious, until
integration tests will be executed
and success is verified.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Thu, Mar 20, 2014 at 8:32 PM, Eric Kolotyluk
eric.koloty...@gmail.com wrote
I am looking for some way to force my integration tests before a
release, without explicitly using a profile.
For example,
plugin
artifactIdmaven-release-plugin/artifactId
configuration
preparationGoalsclean verify site/preparationGoals
/configuration
On 21 March 2014 06:02, Eric Kolotyluk eric.koloty...@gmail.com wrote:
I am looking for some way to force my integration tests before a release,
without explicitly using a profile.
[del]
Is there some way I can trigger the integration tests when doing a release
mvn release:prepare
/artifactId
/plugin
/plugins
/build
profile
So only during release:perform your integration tests will be executed
and success is verified.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http
On Thu, Mar 13, 2014 at 4:54 AM, Alex Karasulu akaras...@apache.org wrote:
Hello,
I've got a module that builds an executable jar file using the Maven
Assembly Plugin. I'm trying to setup an integration test (in the same
module) that runs this executable jar file as a separate process and
You could use test resource filtering to put the path into a resource file
on the test classpath.
That way the IDE will pick up the same path.
On Thursday, 13 March 2014, Alex Karasulu akaras...@apache.org wrote:
Hello,
I've got a module that builds an executable jar file using the Maven
If you are using Eclipse you could also pass the system property directly
to the JRE. ( Windows/Preferences/installed JRE/ edit /default VM arguments)
It require less work than putting it in all run configuration, but all your
process will have it.
On Thu, Mar 13, 2014 at 8:56 AM, Stephen
Well with Netbeans you just add the following:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version${surefire.version}/version
configuration
Hello,
I've got a module that builds an executable jar file using the Maven
Assembly Plugin. I'm trying to setup an integration test (in the same
module) that runs this executable jar file as a separate process and
interacts with it. To fire up the executable jar file, my integration test
__
Place long winded disclaimer here Date: Fri, 23 Nov 2012 01:55:57 -0800
From: mittiprove...@yahoo.se
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server
specific methods
Here is how I'm using
: Re: DAO injection in integration tests with a few database server
specific methods
Here is how I'm using the injected custom DAO bean method:
public ListNavbarLanguage findWithNavbar(Navbar navbar) {
if (navbarLanguageCustomDao != null) {
return
+0200
From: markku.saar...@iki.fi
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server
specific methods
Use Spring and Hibernate list for questions related on those.
Markku
On 11/24/2012 05:36 PM, Martin Gainty wrote:
that *should
accepter aucune responsabilité
pour le contenu fourni.
Date: Sat, 24 Nov 2012 19:42:49 +0200
From: markku.saar...@iki.fi
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server
specific methods
Use Spring and Hibernate list for questions related
Thanks for your sharing, I have posted on the Hibernate forum,
https://forum.hibernate.org/viewtopic.php?f=1t=1024833 Thanks for the
interest.
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods
specific sql statement.
Kind Regards,
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732594.html
Sent from the Maven - Users mailing list archive at Nabble.com
in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732594.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
[com.thalasoft.learnintouch.core.dao.oracle.NavbarLanguageCustomDao] for
property 'navbarLanguageCustomDao': no matching editors or conversion
strategy found
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods
My mistake... The custom DAO bean implementation class was missing the
implements NavbarLanguageCustomDao statement. I added it. No more exception
any more !
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server
though :-)
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732611.html
Sent from the Maven - Users mailing list archive at Nabble.com
the Oracle specific DAO methods sit in a different Java package ?
Should there be a different resource xml file to have the beans for the
integration tests injection of these specific DAO methods ?
Here is my setup as of today:
The abstract test class:
@ContextConfiguration(locations
package ?
Should there be a different resource xml file to have the beans for the
integration tests injection of these specific DAO methods ?
Here is my setup as of today:
The abstract test class:
@ContextConfiguration(locations = { classpath:spring-hibernate.xml,
classpath:spring-hibernate
[mailto:ljnel...@gmail.com]
Gesendet: Freitag, 27. Juli 2012 17:31
An: Maven Users List
Betreff: Re: Failsafe Plugin: How to get resource dependencies for
integration-tests?
On Fri, Jul 27, 2012 at 7:27 AM, Martin Gainty mgai...@hotmail.com wrote:
Marcus
you can copy applicable resources
An: Maven Users List
Betreff: Re: Failsafe Plugin: How to get resource dependencies for
integration-tests?
On Fri, Jul 27, 2012 at 7:27 AM, Martin Gainty mgai...@hotmail.com
wrote:
Marcus
you can copy applicable resources with maven-resources-plugin
http://maven.apache.org/plugins/maven
Good point! :-)
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Montag, 30. Juli 2012 16:11
To: Maven Users List
Subject: Re: Failsafe Plugin: How to get resource dependencies for
integration-tests?
I suggest binding to the pre-integration
Hello Maven Community,
I have a complex setup to do for an end-to-end integration test. For
this, I am using the Maven Failsafe plugin. As the test needs some
resources to run (which I plan to put into Nexus as this feels just
natural), I want to tell Maven that when the integration test is
: How to get resource dependencies for
integration-tests?
Date: Fri, 27 Jul 2012 15:06:06 +0200
From: k...@quipsy.de
To: users@maven.apache.org
Hello Maven Community,
I have a complex setup to do for an end-to-end integration test. For
this, I am using the Maven Failsafe plugin
natural), I want to tell Maven that when the integration test is
running, it shall download them and put them on the HDD. Is there a way
to specifiy such intergration-test-scoped dependencies?
I am unaware of any such integration-test scope for dependencies. I
would just use test scope for
On Fri, Jul 27, 2012 at 7:27 AM, Martin Gainty mgai...@hotmail.com wrote:
Marcus
you can copy applicable resources with maven-resources-plugin
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.htmljustremember
to hook the phase you want to bind to e.g.
If you don't need resource filtering, you could just put the jar with your
resources on the test classpath, i. e. add a test-scoped dependency to the
module containing the integration test.
Am 27.07.2012 15:06 schrieb Markus Karg k...@quipsy.de:
Hello Maven Community,
I have a complex setup
/executions
/plugin
/plugins
/build
--
View this message in context:
http://maven.40175.n5.nabble.com/configure-unit-integration-tests-order-tp5708894.html
Sent from the Maven - Users mailing list archive at Nabble.com
/configuration
/execution
/executions
/plugin
/plugins
/build
--
View this message in context:
http://maven.40175.n5.nabble.com/configure-unit-integration-tests-order-tp5708894.html
Sent from the Maven - Users mailing list
I want to
- build my maven modules top-down using snapshot dependencies among each other
- start my appserver with cargo
- run the integration-tests and
- keep the appserver running afterwards.
A simplified project structure might look like this
pom.xml
|_ moduleA
|_ moduleB
|_ moduleC
wrote:
I want to
- build my maven modules top-down using snapshot dependencies among each
other
- start my appserver with cargo
- run the integration-tests and
- keep the appserver running afterwards.
A simplified project structure might look like this
pom.xml
|_ moduleA
|_ moduleB
Hi all,
I'm sure I missed something, but when running integration tests using
maven-invoker-plugin, even if integration tests fail, the build
doesn't :(
This[1] is the plugin configuration and the related output[2] I can
get after ran `mvn clean integration-test`
Any hint would be much more than
Never ever run the goals
pre-integration-test
integration-test
post-integration-test
directly from the command line
to run integration tests use
mvn verify
the best practice for using the integration-test phase is to not fail
the build in that phase and defer checking the integration test
-integration-test
integration-test
post-integration-test
directly from the command line
to run integration tests use
mvn verify
the best practice for using the integration-test phase is to not fail
the build in that phase and defer checking the integration test
results until the verify phase
Hello everyone,
I can't build Maven properly with the m2eclipse plugin, below are the errors I
get in Eclipse. Almost all maven subprojects fail to build with m2eclipse...
http://www.ideone.com/vBVg6
With the command line, I can build Maven ok but most of the integration tests
fail
will run in memory and as fast as possible.
I define integration tests as tests that are dependent on other
resources than the source code. This is (at least):
* The file system
* Databases
* Network access
Assume that we are dealing with a multi module build, how would you
organize the modules
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
1 - 100 of 286 matches
Mail list logo
