On Tue, 2009-08-18 at 07:44 +0200, Hans Dockter wrote: > On Aug 16, 2009, at 12:43 PM, Russel Winder wrote: > > > It seems that the :integTest is undertaken even when -Dskip.test=true. > > Is this intentional? A priori I would have though not. > > Sometimes you want to execute the integration tests without executing > the unit tests. Although in our current scenario this doesn't really > work, as the skipping the unit tests prevents compiling the unit > tests, which is the task that also compiles the integration test. So > the integTest task should also depend on compile test. Our new > SourceSet functionality will be a very good fit to model problems like > this one.
On a side note, how long should the integration tests take to run?
Also how long should the unit tests take?
I'm afraid I get so bored waiting for the tests that I do not use
"./gradlew install" to do my installation. Instead I use "./gradlew
-Dskip.test=true clean explodedDist" and then copy stuff. I have a
shell script for this and this is what gives me the weird (i.e.
incomprehensible) compilation errors since the change to using covariant
return types in CopySpecImpl.groovy. But that is for a different
thread :-)
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
