Thanks for the reply Jeffrey.

So far as I can see it would not be possible to completely reuse the test
plugin without any change because it references the pom directly. However
with just a few small tweaks test:test (now renamed test:batch to more
accurately reflect what it does) can be wrapped by 2 new goals named
test:iutest and test:test.

Despite the internal changes test:test will behave as it did previously - so
business as usual.

If this meets with approval I will convert the other targets (test:single,
test:match etc) using a similar approach and update the xdocs. NB These
changes take as their base beta 7.

Tim

----- Original Message -----
From: "Jeffrey D. Brekke" <[EMAIL PROTECTED]>
To: "Turbine Maven Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 12:08 AM
Subject: Re: question on integration unit tests


> On Mon, 13 Jan 2003, Tim Stephenson wrote:
>
> > All,
> >
> > First of all can I check my understanding of the difference between
> > integration unit tests and the regular kind. It seems that IUTs are not
run
> > before the project artifact is created whereas unit tests are. This
seems
> > perfect for the problem I wish to solve, that is to create an EJB jar
with
> > maven, deploy it myself and then run the IUTs (which will test the
deployed
> > ejb).
>
> Your definition on IUT seems reasonable to me except that it may also
> include other project's artifacts to run the iut's also, therefore maybe,
> using a reactor build, a second pass across the projects running the iut's
> may be required.  It just might not be limited to a single project.
>
> > Assuming this is a suitable use of Integration Unit tests, am I missing
it
> > or is there no plugin to run integration unit tests (as identified by
the
> > integrationUnitTestSourceDirectory in the project.xml)?
>
> There is nothing currently that does iut.  Some conversations have sparked
> on the lists about it from time to time, but nothing concrete seems to
> have happened yet.
>
> > If there is none I had 2 possible options for creating one:
> > 1) Copy the test plugin and repoint all the properties to be integration
> > unit test instead of unit test
> > 2) Try to dynamically reset these properties and invoke the existing
plugin
> > (I have no idea at this point if this is possible)
> >
> > Does anyone have comments / advice before I embark on this? Have I
missed
> > the point entirely?
>
> I believe that #2 was being attempted by someone.  It is the better of the
> two choices since it could be almost an exact copy of the test plugin.
>
> >
> >
> > Tim Stephenson
> > Technical Specialist
> > Technology One Limited
> >
> > 67 High St , Toowong 4066
> > Phone:  +61 7 3377 7300
> > Fax:      +61 7 3377 7301
> > E-mail:   [EMAIL PROTECTED]
> > Techone home page at:  http://www.TechnologyOneCorp.com
> > Technology One's entire liability will be limited to resupplying the
> > material enclosed. No other warranties are provided
> >
> > Technology One designs, develops, implements and supports intelligent
> > enterprise wide software applications using Internet, eBusiness and
Client
> > Server technologies for both corporate and government organisations
> >
> >
> > *******************   Confidentiality Statement  *******************
> > The information transmitted in this email is only for the recipient
referred
> > in this email and may contain confidential and/or privileged material.
If
> > you are not the intended recipient (or responsible for delivery of the
> > message to such person), you may not copy or deliver this message to
anyone.
> > In such case any review, retransmission, dissemination or other use of,
or
> > taking of any action in reliance upon, this information by persons or
> > entities other than the intended recipient is prohibited. If you
received
> > this in error, please contact the sender and delete the material from
the
> > computer.
> >
> > Opinions, conclusions and other information in this message that do not
> > relate to the official business of the company shall be understood as
> > neither given nor endorsed by it.
> >
> > We use virus scanning software but exclude all liability for viruses or
> > similar in any attachment.
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
> >
>
> --
> =====================================================================
> Jeffrey D. Brekke                                   [EMAIL PROTECTED]
> Wisconsin,  USA                                     [EMAIL PROTECTED]
>                                                     [EMAIL PROTECTED]
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>

Attachment: plugin.jelly
Description: Binary data

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to