On Tue, 2006-01-31 at 05:26 -0600, Allison, Bob wrote:
I also see a need for being able to inject mock objects of Plexus
components (the RPM plugin uses a Plexus Archiver). The unit test will
need to construct these mock objects and set their expectations before
they are injected into the
I also see a need for being able to inject mock objects of Plexus
components (the RPM plugin uses a Plexus Archiver). The unit test will
need to construct these mock objects and set their expectations before
they are injected into the plugin being tested.
Another item used by the RPM plugin
:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: mardi 31 janvier 2006 01:57
To: Maven Developers List
Subject: Re: unit testing vs integration testing plugins
We probably need to provide some plugin test infrastructure like mock
objects and utilities to do the common test tasks.
On 1/30
Brett Porter wrote:
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and would like to
change that. But most of the tests cropping up seem to be integration
tests, because they are probably an easier mechanism than to setup
I have always kinda figured the rule of thumb regarding tests and artifacts
is unit tests would test anything inside of the artifact and integration
tests would encompass extra-artifact scope testing
and I totally agree, I think unit testing within mojo projects would be a
lot more prelavent with
We probably need to provide some plugin test infrastructure like mock
objects and utilities to do the common test tasks.
On 1/30/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and
It might be nice to have a harness which would allow unit testing
plugins. The only problem is you have to test the test harness...this is
a problem we've run into time and again with all of the test harnesses
we have for Maven. I've personally fixed failures based on assumptions
in the
