From: Luke Daley [mailto:luke.da...@gradleware.com]
Sent: Wednesday, July 16, 2014 8:39 PM
To: KARR, DAVID; dev@gradle.codehaus.org
Subject: RE: [gradle-dev] Confused by part of userguide build process

On 17 July 2014 at 12:59:06 pm, KARR, DAVID 
(dk0...@att.com<mailto:dk0...@att.com>) wrote:
From: Luke Daley [mailto:luke.da...@gradleware.com]
Sent: Wednesday, July 16, 2014 4:58 PM
To: KARR, DAVID; dev@gradle.codehaus.org<mailto:dev@gradle.codehaus.org>
Subject: RE: [gradle-dev] Confused by part of userguide build process

On 17 July 2014 at 9:34:59 am, KARR, DAVID 
(dk0...@att.com<mailto:dk0...@att.com>) wrote:
From: Daz DeBoer [mailto:darrell.deb...@gradleware.com]
Sent: Wednesday, July 09, 2014 11:05 AM
To: dev@gradle.codehaus.org<mailto:dev@gradle.codehaus.org>
Subject: Re: [gradle-dev] Confused by part of userguide build process
On Tue, Jul 8, 2014 at 5:13 PM, KARR, DAVID 
<dk0...@att.com<mailto:dk0...@att.com>> wrote:
From: Daz DeBoer 
[mailto:darrell.deb...@gradleware.com<mailto:darrell.deb...@gradleware.com>]
Sent: Tuesday, July 08, 2014 3:54 PM
To: dev@gradle.codehaus.org<mailto:dev@gradle.codehaus.org>
Subject: Re: [gradle-dev] Confused by part of userguide build process
Yes, you need to update the expected output in 'userguideOutput'.
- In automated testing, the userguideOutput is compared against the actual 
output of executing the gradle command
If I run “gradle docs:userguide”, will that generate the user guide and run the 
tests?  I’m guessing not, as I would have seen errors because of this, if they 
were running.
Correct. These test that exercises the user guide samples is 
org.gradle.integtests.samples.UserGuideSamplesIntegrationTest. This will be run 
by:
'gradle :integTest:check', and you can probably use --tests to run just that 
test.

I can’t get this to work.  I tried several variations of “—tests”, but it’s 
saying “Unknown command-line option '--tests'”.  This is odd, because I 
verified with “gradle –v” that I’m using Gradle 2.0.  I also tried a couple of 
variations on “-Dtest.single=...”, but that just seemed to be ignored.  This 
would execute all of the integration tests, and it appears that most or all of 
those are failing

What’s the exact command line you are using?

gradle :integTest:check --tests 
org.gradle.integtests.samples.UserGuideSamplesIntegrationTest

—tests has to be directly after a test task, so it would be:

gradle :integTest:integTest --tests 
org.gradle.integtests.samples.UserGuideSamplesIntegrationTest



Ok. This is working better.  This particular test is a “mutant” in that it’s 
exercising all of the build script samples in the user guide.  When one fails, 
it prints out the name of the “id” for that sample, so that helps a bit.  Do 
you know if there’s some way to make it ONLY execute a single sample excerpt?

Reply via email to