Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 97469 invoked from network); 26 Mar 2010 07:07:29 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Mar 2010 07:07:29 -0000 Received: (qmail 63304 invoked by uid 500); 26 Mar 2010 07:07:28 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 63175 invoked by uid 500); 26 Mar 2010 07:07:28 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 63167 invoked by uid 99); 26 Mar 2010 07:07:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Mar 2010 07:07:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [217.188.43.21] (HELO fluorine.blau.de) (217.188.43.21) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 26 Mar 2010 07:07:22 +0000 Received: (qmail 6571 invoked from network); 26 Mar 2010 08:07:01 +0100 Received: from unknown (HELO exchange.blau.de.local) (172.20.0.20) by nl.blau.de with SMTP; 26 Mar 2010 08:07:01 +0100 Received: from exchange.blau.de.local ([172.20.0.20]) by exchange.blau.de.local ([172.20.0.20]) with mapi; Fri, 26 Mar 2010 08:07:01 +0100 From: =?iso-8859-1?Q?Peter_Schr=F6der?= To: "users@buildr.apache.org" Date: Fri, 26 Mar 2010 08:07:01 +0100 Subject: Re: enhancing the test task Thread-Topic: enhancing the test task Thread-Index: AcrMsu6v3VX7a9ooQL2G25wPKeozEg== Message-ID: References: <54FF3ED72F41454299EBC44FE688EC20BA7EFFDAF0@exchange.blau.de.local> <4dcd15a91003251543m6e7964cbr92d18dd452702896@mail.gmail.com> In-Reply-To: <4dcd15a91003251543m6e7964cbr92d18dd452702896@mail.gmail.com> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org i am still working through all the examples in the docs from time to time t= o provide some decent examples for our inhouse developers (as can be seen h= ere http://github.com/phoet/buildr-examples) and yesterday i was looking into the testing chapter... there is no usecase that i can think of for this enhancement. i would alway= s prefer putting @Ignore annotations directly in my tests instead of changi= ng the build! btw: "But=3D" in line 3 of the chapter kind regards, peter Am 25.03.2010 um 23:43 schrieb Alex Boisvert: > Yeah, sometimes our documentation is a little, ahem, forward-looking. It > definitely doesn't work on trunk. >=20 > I don't know if this worked before and I'm not sure it's a good use-case. > I'm guessing that if you tried it, it's because there was some appeal to > it? I'd be curious to understand your motivation. >=20 > In any case, the behavior is under-spec'ed right now. It's not clear if > the block should be called if there's a test failure. And if it should = be > called if test=3Dall is passed. >=20 > I'm open to any interpretation on this. We'll update the doc once we rea= ch > a consensus. >=20 > alex >=20 > On Thu, Mar 25, 2010 at 9:42 AM, Peter Schr=F6der wrote: >=20 >> hi, >>=20 >> the buildr docs show an example for enhancing the test-task: >>=20 >> test do >> fail 'More than 3 tests failed!' if test.failed_tests.size > 3 >> end >>=20 >> i did not manage to get that one working and i did not see any spec for = the >> usage. does it really work? >>=20 >> kind regards, >> peter