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 artifact test harness, the project testing harness, and the
PlexusTestCase test harness.
My big worry here is that we'd be building a test harness that didn't
accurately reflect reality, or which would have to be manually
resynchronized with the reality of Maven as it changes. This may
introduce subtle bugs...
Just my 2c.
-john
Jesse McConnell wrote:
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 a simple mechanism of bootstraping the plugin
requirements..
jesse
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 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 the
preconditions of the plugin. However, they are much larger in terms of
creation, checkout space and time to run.
I'd like to see that we "unit test" to the greatest extent possible.
IMO, the only reason to go to integration tests is to test lifecycle
interactions and interactions with other plugins.
What we probably require to do this is convenience methods to construct
a decent project and settings object and an expression populator based
on the project and settings.
Thoughts?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
