Hi Vincent,
Vincent Massol wrote:
Hi Jesse,
[snip]
Now, some of plugins can be completely tested by this mechanism while
others
might not actually fit too tell into this lower level testing. That is
where the integration testing comes into more of a play.
I talked to john about this and we were kind of a mind that stubbing and
mocking up these project objects and whatnot don't represent reality very
well and perhaps the best solution would be to follow the route of the
integration plugin where we can craft little projects in the plugin
directory that represent real life usages of the plugin, then we verify
that
the right thing was done. This verification could take the form of
validating the resulting directory structure matched an outcome, certain
files matched an outcome, or the state of objects in the project matched
the
template.
I agree about not mocking anything for integration testing. How is that
different from what the it and verifier plugin currently do?
It's possible that we already have everything we need for executing and
verifying integration tests, though I'd really like to see options for
setup and tear-down of the environment as well. However, more to the
point, I think we need to provide some sort of archetype or something to
bring all of these myriad solution-parts together into something people
can easily hook into for testing...with minimal fuss.
Thanks for starting this discussion, Jesse. It's really important that
we get this sorted out soon, so we can bring plugin development out of
the stone age! :-)
My 2c.
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
