On 1/03/10 7:33 AM, Peter Ledbrook wrote:
Hi,
I had a quick stab at extracting the integration test classes into a
separate module:
http://github.com/pledbrook/gradle/commit/9e20e7bbe61aad6722b73ed8eda810cb2ef9e5d7
I haven't included AbstractIntegrationTest.groovy, but it should be
added in some form I think. Anyway, I'm using the module to create
integration tests for the 'grails-build' plugin.
Let me know what you think, including suggested changes etc.
I think this is a really good thing to have. We want to make plugin
development as easy as possible, and integration testing is an important
part of this.
Some comments:
- There are now 2 copies of the test classes. The Gradle integration
tests should use the classes out of gradle-test project, rather than
using a copy of them.
- These classes will need some unit tests at some point. But I think we
can add them as we need them.
- How will you use these classes from your own build? This feels like
the kind of jar that should just live in a repository, rather than being
included in the Gradle distribution.
- We probably should review the API at some point. It really just grew
organically as the integration tests needed stuff without too much
thought. Given that GradleLauncher/StartParameter and GradleExecuter are
doing more or less the same thing, we should see if we can get a common
API which is shared by them.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
