I'm also highly interested in this and can help out. I found when writing the dependency plugin that I needed to write a lot of mock objects. The nice thing about Maven is that almost everything is an interface, which makes it fairly trivial to implement anything you need to fully exercise your code. Some handy things like stub factories to create artifacts or dependencies would be nice. In fact, I have a pretty large set of them already between dependency and enforcer that could be shared.
I think missing from the various invoker scenarios is an easy way to control settings in a generic way and to deal with pretend remote and local repositories. I found the plugin harness wasn't entirely useful. It required the overhead of creating poms like the invoker, but didn't seem to set my parameters correctly. I ended up using the harness to get a mojo and then just used setters to control the various inputs directly in my tests. It made it much easier to deal with all the permutations that way. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Saturday, April 21, 2007 3:52 PM To: Maven Developers List Subject: Re: maven-component-it-plugin, what is it, what does it do? I was going to take a stab at writing the definitive "how to write plugin integration tests" document when I did it for surefire (after I get back from holidays.... still another week + conferences to go yet :) I'm not going to complain if someone starts it first :) Between yourself, Brian, John and I (maybe others, those are the names I've noticed discussing it recently), we should be able to pull this together for everyone to use. As I understood it, there were still problems with this approach - that it was slow? We'll need both a unit testing (cleaned up plugin harness) and integration testing (invoker based) solution, then. There is also the list of stuff in SVN under the integration tests which is highly related. Did I catch everything? - Brett On 21/04/2007, at 11:30 AM, Barrie Treloar wrote: > the assembly plugin is using it, it looks like to stage the plugin for > it testing. > > Is this plugin coming out of the sandbox at some stage and be > documented? > > I have no idea how to use it, etc. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
