You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Zeleznik <dz...@ilog.com> on 2003/03/17 21:56:19 UTC
integrationUnitTest
Hi,
I asked this question last week, but received no response. So here it is
again slightly rephrased. The <integrationUnitTestSourceDirectory> and
<integrationUnitTest> elements are described in the project schema. They are
defined exactly the same as the <unitTestXXX> elements and, in fact, several
of the project.xml's within Maven itself contain them. However, they are not
used anywhere and only <integrationUnitTestSourceDirectory> is actually
implemented as a property in Build.java, <integrationUnitTest> is not.
Are the <integrationUnitTestXXX> elements deprecated or are they in process
of being implemented for a future Maven version? We would like to take
advantage of these elements to segregate our tests (via different
includes/excludes) into 2 separate categories: routine tests and more
extensive integration tests. However, we are unable to use the
<integrationUnitTest> element because it is not currently implemented in
Build.java. The only avenue I see is to create a separate pom in each
project to define the integration tests. Any suggestions for a cleaner or
better way to handle this?
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
RE: integrationUnitTest
Posted by David Zeleznik <dz...@ilog.com>.
Hi Jeffrey,
> If you dig back into the logs there was someone working to do just
> that and reuse the test plugin. I'm not sure of the status which is
> why I didn't respond the first go around. I have the same use case is
> you, we want our slower running 'program integration tests' to be
> available but not run with our 'unit tests'.
>
> There was talk of offering something like any number of levels of
> tests, not just two.
Thanks for the hint- I just reviewed the relavent discussion threads from
January. However, it does not seem that there is any active work going on in
this area. I do not see any further mention from the person that said he had
something for beta7.
I've looked a bit more at our situation. Currently, we have all our unit and
integration tests for a particular project stored in the same directory
tree. This is a holdover from Ant when we simply ran all the tests at night
via a cron job. So, our unit tests can be considered as a strict subset of
the integration tests. So, what I am now thinking is that our project.xml
would contain the <unitTest> fileset definition for all the tests, ie. the
integration tests. Then we could define a project property that contains an
additional exclude pattern that will refine the integration tests into the
unit tests. I am not sure if it is possible to modify the pom
programmaticly, but I am going to try doing something like:
<j:set var="dummy"
value="pom.build.unitTest.addExclude(myExcludePatternProp)" />
in a test pregoal. This might serve my needs adequately for now.
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
> >>>>> On Mon, 17 Mar 2003 15:56:19 -0500, "David Zeleznik"
> <dz...@ilog.com> said:
>
> > Hi, I asked this question last week, but received no response. So
> > here it is again slightly rephrased. The
> > <integrationUnitTestSourceDirectory> and <integrationUnitTest>
> > elements are described in the project schema. They are defined
> > exactly the same as the <unitTestXXX> elements and, in fact, several
> > of the project.xml's within Maven itself contain them. However, they
> > are not used anywhere and only <integrationUnitTestSourceDirectory>
> > is actually implemented as a property in Build.java,
> > <integrationUnitTest> is not.
>
> > Are the <integrationUnitTestXXX> elements deprecated or are they in
> > process of being implemented for a future Maven version? We would
> > like to take advantage of these elements to segregate our tests (via
> > different includes/excludes) into 2 separate categories: routine
> > tests and more extensive integration tests. However, we are unable
> > to use the <integrationUnitTest> element because it is not currently
> > implemented in Build.java. The only avenue I see is to create a
> > separate pom in each project to define the integration tests. Any
> > suggestions for a cleaner or better way to handle this?
>
> > -------------------------------------- David Zeleznik ILOG -
> > Changing the rules of business mailto:dzeleznik@ilog.com
> > http://www.ilog.com --------------------------------------
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > turbine-maven-user-unsubscribe@jakarta.apache.org For additional
> > commands, e-mail: turbine-maven-user-help@jakarta.apache.org
>
> --
> =====================================================================
> Jeffrey D. Brekke jbrekke@wi.rr.com
> Wisconsin, USA brekke@apache.org
> ekkerbj@yahoo.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> turbine-maven-user-help@jakarta.apache.org
>
Re: integrationUnitTest
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
If you dig back into the logs there was someone working to do just
that and reuse the test plugin. I'm not sure of the status which is
why I didn't respond the first go around. I have the same use case is
you, we want our slower running 'program integration tests' to be
available but not run with our 'unit tests'.
There was talk of offering something like any number of levels of
tests, not just two.
>>>>> On Mon, 17 Mar 2003 15:56:19 -0500, "David Zeleznik" <dz...@ilog.com> said:
> Hi, I asked this question last week, but received no response. So
> here it is again slightly rephrased. The
> <integrationUnitTestSourceDirectory> and <integrationUnitTest>
> elements are described in the project schema. They are defined
> exactly the same as the <unitTestXXX> elements and, in fact, several
> of the project.xml's within Maven itself contain them. However, they
> are not used anywhere and only <integrationUnitTestSourceDirectory>
> is actually implemented as a property in Build.java,
> <integrationUnitTest> is not.
> Are the <integrationUnitTestXXX> elements deprecated or are they in
> process of being implemented for a future Maven version? We would
> like to take advantage of these elements to segregate our tests (via
> different includes/excludes) into 2 separate categories: routine
> tests and more extensive integration tests. However, we are unable
> to use the <integrationUnitTest> element because it is not currently
> implemented in Build.java. The only avenue I see is to create a
> separate pom in each project to define the integration tests. Any
> suggestions for a cleaner or better way to handle this?
> -------------------------------------- David Zeleznik ILOG -
> Changing the rules of business mailto:dzeleznik@ilog.com
> http://www.ilog.com --------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> turbine-maven-user-unsubscribe@jakarta.apache.org For additional
> commands, e-mail: turbine-maven-user-help@jakarta.apache.org
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com