One approach could be to have a main() overload taking an additional
Environment argument to abstract access to environment variables, system
properties, and standard I/O; and returning an int as the possible
System.exit() value.
That way, you can easily stub the environment for tests.
Your standar
It depends on the criticality of your command line tools. One
interessting approach is the one by the SpringBoot guys. They run
commands in a Docker container and collect stdout to check the behaviour
of their System V start script.
=>
https://github.com/spring-projects/spring-boot/blob/9d078
Have you considered writing an integration test that invoked your command
line tool from the command line?
When you use tools like Failsafe, JUnit, etc, you can know that the process
works in that environment, but the real world execution won't be the same.
While most of your corner cases, logic,
When writing integration tests for command-line tools, is there any
support in Failsafe, jUnit, or elsewhere to fork a process and manage
its standard IO streams?
Or am I over-designing? Would one typically write such an integration
test rather like a unit test, bypassing the command analyzer and
I'm trying (but failing) to reliably test a reporting plugin that
requires some code analysis to be done to produce report input. (code
analysis produces xml that is xsl transformed to html)
Sometimes my test works, sometimes it doesn't; the test just uses the
org.apache.maven.it.Verifier#veri
Hi Jason,
Absolutely, my apologies. I didn't mean to imply anything about Takari
specifically. Your efforts, as always, are fantastic and a real credit to
the OSS community. I was speaking more philosophically about the scope of
the list in general.
And actually, I think Manfred and I are not rea
On Feb 27, 2015, at 3:15 PM, Curtis Rueden wrote:
> Hi Manfred,
>
>> I think the same should apply for all other plugins.
>
> By that logic, an Ubuntu Linux mailing list should answer all questions
> about all packages available for Ubuntu, even multiverse packages. Seems
> impossible to me.
>
Yes... but we should be inclusive and generally allowing the questions and were
needed redirect to better forums if we are aware of them.
And when comparing it to Ubuntu... there are the big mailing lists that answer
all these kind of questions are a general busy hub of everything.
I think su
Hi Manfred,
> I think the same should apply for all other plugins.
By that logic, an Ubuntu Linux mailing list should answer all questions
about all packages available for Ubuntu, even multiverse packages. Seems
impossible to me.
That said, of course the people here are friendly and make a best
Olivier Lamy wrote on 26.02.2015 15:26:
> As it looks the question is related to an other project which is not hosted
> within the Apache Maven project neither developed by Apache Maven
> committers.
> I believe this mailing list is related to the Apache Maven project.
> So my goal was only to h
On 27 February 2015 at 06:00, Manfred Moser wrote:
> Cristiano,
>
> You can have them all in one project. E.g. the Android Maven Plugin does
> that.
>
> https://github.com/simpligility/android-maven-plugin
>
> Olivier,
>
> I thought this is a Maven users mailing list and as such open to all
> que
Yes, I wonder the same thing, any maven question can be posted here.
-D
On Thu, Feb 26, 2015 at 11:00 AM, Manfred Moser
wrote:
> Cristiano,
>
> You can have them all in one project. E.g. the Android Maven Plugin does
> that.
>
> https://github.com/simpligility/android-maven-plugin
>
> Olivier,
Cristiano,
You can have them all in one project. E.g. the Android Maven Plugin does that.
https://github.com/simpligility/android-maven-plugin
Olivier,
I thought this is a Maven users mailing list and as such open to all questions
regarding usage of Maven. I would understand the need to separ
Hi,
AFAIK this Takari project is not hosted neither maintained here at Apache
by Apache Maven developers.
So for any questions please ask directly maintainers or find a user group
related to it (maybe it's documented on their website).
Cheers
Olivier
On 26 February 2015 at 03:52, Cristiano Gavião
Hi,
It is necessary to concentrate the maven plugin integration tests in its
own takari-jar project ?
I'm asking because I have test poms inside src/test/projects being
duplicated on both Plugin and Plugin IT projects.
Maybe I could put both UT and IT in the same plugin project ?
thanks,
I just started using it for my internal plugin, will eventually use it at
MOJO
-D
On Fri, Jan 16, 2015 at 1:33 PM, Manfred Moser wrote:
> We are glad you enjoy using it. If you have any feedback or suggestions
> regarding the plugin, documentation and so on please create issues related
> proj
We are glad you enjoy using it. If you have any feedback or suggestions
regarding the plugin, documentation and so on please create issues related
projects on github.
https://github.com/takari/takari-lifecycle
https://github.com/takari/takari-plugin-testing-project
It would also be great if yo
Thanks!
On Jan 16, 2015, at 12:43 PM, Dan Tran wrote:
> I started to use this plugin for my plugin IT test. Writing maven plugin is
> now much more fun
>
> Very much appreciate the work
>
>
> -Dan
Thanks,
Jason
--
Jason van Zyl
Founde
I started to use this plugin for my plugin IT test. Writing maven plugin is
now much more fun
Very much appreciate the work
-Dan
> My problem is that things can go wrong in pre. When they do, the build
> fails, and then post doesn't run, and the early parts of pre that
> succeed don't get cleaned up.
pre should fail the build and clean it up itself. It might be
difficult if there are multiple mojo binded to pre-integration-t
I have the classic integration testing structure under construction:
pre
test
post
My problem is that things can go wrong in pre. When they do, the build
fails, and then post doesn't run, and the early parts of pre that
succeed don't get cleaned up.
I could probably fig
end on those modules in your War
project. Localize unit and integration testing within the Jar module
if possible.
What is the recommended aproach to organize integration testing in a maven
multi-module webapp project?
You can still do integration testing with your War file. But this
should me
mean the
> only way to go is have nearly-empty WARs with all classes in other modules,
> on which the WAR depends?
This is the "correct" way to set things up. Put your class files in
one or more Jar modules and then depend on those modules in your War
project. Localize unit and
of my
WAR module to JAR, and the test module picked up all transitive
dependencies...)
What is the recommended aproach to organize integration testing in a
maven multi-module webapp project?
Thanks and have a good day,
Alex
--
n 3.X, what's the current recommended way to
> do the IT in terms of layout/plugin?
>
> Thanks!
>
> -Guo
>
> [1]
> http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
> [2]
> http://docs.codehaus.o
Happy New Year everyone,
maven-failsafe-plugin was used in [1] to perform IT. Both [1] and [2]
mentioned src/it/java, in 3.X, what's the current recommended way to
do the IT in terms of layout/plugin?
Thanks!
-Guo
[1] http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testi
I'm interested in knowing the current thinking on best practices for
> integration testing in Maven projects. I did find a few articles on the Web
> that discuss this issue, but they all are a bit old now. The most relevant
> article appears to be this one:
>
> http://docs.co
[mailto:adam.ma...@cyberspaceroad.com]
Gesendet: Donnerstag, 9. April 2009 11:41
An: Maven Users List
Betreff: Re: AW: Integration testing best practices
I use (3) as well.
I haven't got many integration tests - I just do it to make sure it works. But
I'd be interested to find out what kind of m
I use (3) as well.
I haven't got many integration tests - I just do it to make sure it works. But
I'd be interested to find out what kind of metrics and reports people use when
doing intensive integration testing.
Rouvinez, Jean-Claude on 09/04/09 07:42, wrote:
Hi,
We use the
Hi,
We use the solution 3 suggested under
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing?focusedCommentId=114787113#comment-114787113
and it works for us.
This article is not so old (Jan 09).
Best Regards
Jean-Claude
-Ursprüngliche Nachricht-
Von: Jason
On Wed, Apr 8, 2009 at 10:22 AM, Jason Voegele wrote:
> I'm interested in knowing the current thinking on best practices for
> integration testing in Maven projects. I did find a few articles on the Web
> that discuss this issue, but they all are a bit old now. The most rele
I'm interested in knowing the current thinking on best practices for
integration testing in Maven projects. I did find a few articles on the Web
that discuss this issue, but they all are a bit old now. The most relevant
article appears to be this one:
http://docs.codehaus.org/di
Thanks, Wendy! I must have been blind to miss that option in my xml editor.
That was the trick.
Wendy Smoak wrote:
On Thu, Feb 5, 2009 at 3:07 PM, David C. Hicks wrote:
Essentially, I have two modules - the "war" module and the
"integration-test" module. (I intend to split the war stuff u
On Thu, Feb 5, 2009 at 3:07 PM, David C. Hicks wrote:
> Essentially, I have two modules - the "war" module and the
> "integration-test" module. (I intend to split the war stuff up soon, as
> well.) Obviously, the "integration-test" module must have a dependency on
> "war" (it can't run tests if
I'm trying to set up a module for my team from which to run integration
tests, but I can't quite get Maven to like it. It complains that it
cannot find a dependency - the WAR file that is required for the tests
to run.
Essentially, I have two modules - the "war" module and the
"integration-t
-plugin
2.3
etc...
maxmil wrote:
>
> I'm not a maven expert so maybe i'm doing something wrong but if not i may
> have found a bug.
>
> I configure integration testing via a build profile as follows:
>
>
>ite
I'm not a maven expert so maybe i'm doing something wrong but if not i may
have found a bug.
I configure integration testing via a build profile as follows:
itest
itest
org.apache.maven.plugins
maven-suref
I am getting started with Maven 2. I currently use a Groovy +
AntBuilder build for my projects.
I create parallel projects.
/codearea
/pack
/strata
/depot
Let's say the "depot" project depends on "strata" which depends on
"pack". I can cd to depot and run...
./builder siblingTest
Um, ignore my last email - I realize now I was just making a bad
assumption based on the lifecycle concept. The contents of that blog
do pretty much exactly what I want.
-db
On Jan 24, 2008, at 5:26 PM, David Bock wrote:
I was a Maven 1 user on a couple of project a long time ago - I'm
n
I was a Maven 1 user on a couple of project a long time ago - I'm now
upgrading my skills to Maven 2, and also managing the build process
for a straightforward web app deploying into WebSphere.
I have a top-level project with a bunch of sub-projects... one of
which is a set of functional t
Hi there,
I was wondering if anyone has explored running Seam 2 integration
tests through Maven? I have been able to setup a Maven2+Seam2 project
and have executed it without any problems, but after playing around
with the the Seam2 integration test examples I have not been able to
execute any te
, "during your integration test phase, install reg-srv and
start it up THEN run your own integration tests"??
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 2:40 PM
To: Maven Users List
Subject: integration testing
I'm kinda d
I'm kinda dancing around a local solution, but how is the rest of the
maven world doing something like integration tests where the tests
require a running instance of the code they're trying to test?
We have things like registry services that we'd like to integration
test, but the tests would req
I may never know :)
I had thought of a similar approach, but some JDBC drivers are actually
mutliple jars...
On Fri, 2007-05-25 at 11:32 +0100, Pete wrote:
> I'm not sure I understand at which point you do know these 'execution
> environments' but maybe you could specify the values on the com
I'm not sure I understand at which point you do know these 'execution
environments' but maybe you could specify the values on the command
line along with a pom as follows :-
${jdbc.groupId}
${jdbc.artifactId}
${jdb
I am looking to migrate Hibernate to use Maven for building. I am
currently running into a problem porting the Hibernate testsuite. The
Hibernate testsuite is mainly a bunch of functional and integration
tests and not really unit tests per-se. But it is built on top of
Junit.
Anyway, the proble
With most of my problems with Maven it is a combination of:
- Better builds with Maven e-book [1]
- Sonatype e-book [2]
- The plugin documentation [3] [4]
- The Maven 2 IRC channel [5]
And offcourse, this userlist, maven 2 and plugins sourcecode
Hth,
Nick Stolwijk
[1] http://www.mergere.com/m2
Nick, et al...
Thanks for the suggestion...
But I have to ask a meta-question: how was I supposed to ever find
that myself...? It's nowhere in the Surefire plugin documentation...
I still don't even know that it will work, nor does the documentation
give any hint that it might.
And to bring th
Maybe this'll work:
org.apache.maven.plugins
maven-surefire-plugin
2.3
surefire-test
test
surefire-integration-test
integration-test
src/itest/java
Ok guys...
Am I running against "best practices" here? Is that why this is so hard?
I have a simple-ish project. The project artifact is a WAR file. I
would like to Unit Test the code before it gets packaged, and I would
like to run Integration Tests after it gets packaged.
The Sonatype book
Hi,
I am trying Integration testing for the first time in Maven.
I need to write a profile to integrate test dependencies into build and
deploy build locally and then run integration tests with Clover ON for code
coverage.
Any examples or ideas on achieving the same?
Thanks and regards
Raju
ardi 6 mars 2007 01:24
To: Maven Users List
Subject: RE: Using the POM classpath for integration testing
[Please refer to the fitnesse thread regarding the fitnesse usage
questions]
Coming back to Maven2,...
Since I would like to keep my acceptance pages along with my source
files, I think I
nt: Monday, March 05, 2007 7:44 PM
To: [EMAIL PROTECTED]; Eric Torreborre
Subject: RE: Using the POM classpath for integration testing
This is a thread that starts on Maven list.
I transfer it because it more a debate about our use/pros/cons of
fitnesse than a Maven2 discussion.
Our process is:
Before
This thread will continue on [EMAIL PROTECTED]
-Original Message-
From: Eric Torreborre [mailto:[EMAIL PROTECTED]
Sent: lundi 5 mars 2007 06:09
To: Maven Users List
Subject: RE: Using the POM classpath for integration testing
Hi Philippe,
Here is the setup I have in mind. Not only
PROTECTED]
Sent: Monday, March 05, 2007 6:42 AM
To: 'Maven Users List'
Subject: RE: Using the POM classpath for integration testing
Hi Eric,
I our approach there is always a centralized FitNesse server running.
This server is available for all project people, including non
developers.
Our two
the time being ;-)
-Original Message-
From: Eric Torreborre [mailto:[EMAIL PROTECTED]
Sent: vendredi 2 mars 2007 02:05
To: Maven Users List
Subject: RE: Using the POM classpath for integration testing
Hi Philippe,
Thanks for your answer.
I had not seen -your- m
: Using the POM classpath for integration testing
Philippe,
By the way,
I had a different approach for executing the Fitnesse tests. I wrote a
FitnessePageRunner class based on the FolderRunner class in the
fitlibrary.
This way, I don't have to launch a web server to do the job.
The
lippe Kernevez [mailto:[EMAIL PROTECTED]
Sent: Friday, March 02, 2007 2:36 AM
To: 'Maven Users List'
Subject: RE: Using the POM classpath for integration testing
Hi Eric,
Do you speak about the fitnesse-maven-plugin ? I suppose that's the
case.
The plugin doesn't use the POM
'Maven Users List'
Subject: RE: Using the POM classpath for integration testing
Hi Eric,
Do you speak about the fitnesse-maven-plugin ? I suppose that's the
case.
The plugin doesn't use the POM dependencies because they are supposed to
be specified in the Fitnesse page.
The plugin
M classpath for integration testing
Hi,
I have written a simple maven plugin that runs Fitnesse pages during the
integration-test phase.
However, it looks like this plugin, when executed, does not find the
classes that should be provided by the POM (along with dependencies).
Is there is configurat
Hi,
I have written a simple maven plugin that runs Fitnesse pages during the
integration-test phase.
However, it looks like this plugin, when executed, does not find the
classes that should be provided by the POM (along with dependencies).
Is there is configuration that should be done, in order
franz see <[EMAIL PROTECTED]> writes:
> Good day to you, Arnaud,
>
Good day to you too Franz,
> Solution:
> I think the expected transitive dependency was broken. You may want to
> declare the binary containing the "NoClassDefFoundError class" as a direct
> dependency of your project. ..also, yo
.. 30 more
>
> Here is my pom:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>
Hello,
I am trying to add some integration tests for a plugin I wrote, using
MavenEmbedder. When running the test, I got the following impressive
exception trace:
---
Test set: oqube.patchwork.it.PatchworkMavenTest
--
Hello,
We are in the process of enabling code coverage in our projects (Maven 2
projects). Everything works well using the Cobertura plugin for unit
tests. We would like to use Cobertura to measure coverage when running
integration tests as well. For example, let's say we have a
multi-module
Thank you very much for all this informations guys.
++
Julien
- Message d'origine
De : Wendy Smoak <[EMAIL PROTECTED]>
À : Maven Users List
Envoyé le : Vendredi, 24 Novembre 2006, 17h41mn 48s
Objet : Re: Starting/Stopping Jetty for integration testing
On 11/24/06, J
On 11/24/06, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
Where could i find information about TestSetup and example in shale,
i have searched in the shale source repository, but can't find it.
TestSetup is a JUnit thing, so consult JUnit docs and tutorials for
info on that. Generally, the usua
TECTED]> wrote:
> I want to execute jetty:run at the pre-integration-test phase and stop
it (like Ctrl+C) at the post-integration-test phase.
In addition to the plugin that has already been mentioned, Cargo also
has a Java API that can be very useful for integration testing.
Inste
ul for integration testing.
Instead of binding plugin executions to lifecycle phases, you can
start and stop containers from Java code, for example in JUnit
TestSetup class.
Here's an example:
http://shale.apache.org/shale-test/apidocs/org/apache/shale/test/cargo/CargoTestSetup.html
http://svn
If you want this feature, you can't use jetty:run, but you need to use the
cargo plugin.
jetty:run start only a jetty server like you do it without maven.
Emmanuel
Julien HENRY a écrit :
Hi,
I want to execute jetty:run at the pre-integration-test phase and stop it (like
Ctrl+C) at the post-i
On 24/11/06, Julien HENRY <[EMAIL PROTECTED]> wrote:
I want to execute jetty:run at the pre-integration-test phase and stop it (like
Ctrl+C) at the post-integration-test phase.
The problem is jetty:run wait for being killed undefinitly and integration-test
phase is never executed.
I don't kno
Hi,
I want to execute jetty:run at the pre-integration-test phase and stop it (like
Ctrl+C) at the post-integration-test phase.
The problem is jetty:run wait for being killed undefinitly and integration-test
phase is never executed.
I don't know exactly how to do this. It may need to develop a
unit tests and stop at the end of those. I believe
this should be possible using some plugin configuration in m2, right?
It would make life easier for integration testing, as I wouldn't have
to start/stop my HSQLDB on the side... How are you guys dealing with
this kind of issue?
Thanks i
That's perfect
Thanks
Donnchadh
On 9/12/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 9/12/06, Donnchadh Ó Donnabháin <[EMAIL PROTECTED]> wrote:
> I've added the following to :
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
>
On 9/12/06, Donnchadh Ó Donnabháin <[EMAIL PROTECTED]> wrote:
I've added the following to :
org.apache.maven.plugins
maven-surefire-plugin
integration-test
test
This results
I've added the following to :
org.apache.maven.plugins
maven-surefire-plugin
integration-test
test
This results in my tests being executed during the integration-test
phase, which is grea
testsuite and issue: ant tests
At which time our entire testsuite will run, performing integration testing for
all configurations. I can't take away that functionality.
SOto achive this, it sounds like I need to write a plugin which allows many
executions, where
For each execution
> -Original Message-
> From: Ruel Loehr [mailto:[EMAIL PROTECTED]
> Sent: jeudi 31 août 2006 16:10
> To: Maven Users List
> Subject: RE: Integration Testing
>
> I appreciate the feedback. I think these are all valid workarounds, but
> have my concerns about sca
tests
At which time our entire testsuite will run, performing integration testing for
all configurations. I can't take away that functionality.
SOto achive this, it sounds like I need to write a plugin which allows many
executions, where
For each execution
a) configure server an
Sent: Wednesday, August 30, 2006 1:33 PM
To: Maven Users List
Subject: Integration Testing
I'd like to query the community and see how you guys are handling
integration testing in real world environments.
I've looked through the list and the Better builds book, but didn't like
w
> -Original Message-
> From: Heck, Joe [mailto:[EMAIL PROTECTED]
> Sent: mercredi 30 août 2006 22:54
> To: Maven Users List
> Subject: RE: Integration Testing
>
> We have several different mechanisms running - but most of them are
> honestly manual. The automa
Joe Heck wrote
The "how to" for the separate functional test module setup was on this
earlier - the big pieces to note being that the functional test module
is set with POM packaging, and then plugins manually bound to the
various steps (in this case, the maven-surefire-plugin bound to the
integr
of maven with a custom AntTask bound in there to do setup/teardown kinds
of work.
-joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ruel Loehr
Sent: Wednesday, August 30, 2006 1:33 PM
To: Maven Users List
Subject: Integration Testing
I'd li
I'd like to query the community and see how you guys are handling
integration testing in real world environments.
I've looked through the list and the Better builds book, but didn't like what I
saw..
Here is the use case:
Use Case A:
A user has a project which buil
derstand how to best do integration testing with Maven
> 2.x. I am using the pre-integration-test and post-integration-test
> phases to execute a plugin goal that I wrote to deploy some EJBs to a
> container. These EJBs are used in the integration test.
>
> Now, how do I run the tests w
I'm trying to understand how to best do integration testing with Maven
2.x. I am using the pre-integration-test and post-integration-test
phases to execute a plugin goal that I wrote to deploy some EJBs to a
container. These EJBs are used in the integration test.
Now, how do I run the
Hi Pablo,
> -Original Message-
> From: Pablo [mailto:[EMAIL PROTECTED]
> Sent: jeudi 5 janvier 2006 10:43
> To: Maven Users List
> Subject: Integration testing
>
> Hello everyone
>
> I'm trying to include integration tests into my maven project.
> I&
TECTED]
> Sent: 05 January 2006 10:43
> To: Maven Users List
> Subject: Integration testing
>
> Hello everyone
>
> I'm trying to include integration tests into my maven project.
> I've accomplished the task but had to write my own plugin.
> Since I don'
Hello everyone
I'm trying to include integration tests into my maven project.
I've accomplished the task but had to write my own plugin.
Since I don't know maven2 too well I'd like to ask you a few questions.
My plugin does the following:
1) compiles integration tests
2) starts tomcat using carg
At 01:12 PM 9/8/2005, Craig McDaniel wrote:
One approach I've seen is to create *-acceptance projects to contain
the integration tests. For example, da-hibernate-acceptance. I would
end up with no tests in da-hibernate, and only tests in
da-hibernate-acceptance. Is this common? With this setup,
I've seen a few slide presentations on best practices for multiproject
organization, but I was wondering if there is one that is endorsed by
the maven team/community?
I am working on a project that will provide a centralized hub of data
services (JMS, SOAP, JSP) for integrating multiple external s
I have noticed that has been
deprecated. What is good solution for running unit tests and
integration tests separately? Is there a way to do this without a lot
of ant scripting in maven.xml? I am using Maven 1.0.2
--
Craig McDaniel
---
92 matches
Mail list logo
