This says "environment variable" @t...@. Does that mean that Buildr
is checking for a shell variable named "test" ( ENV['test'] )? If so,
shouldn't this be a less ambiguously named variable like BUILDR_TEST?
Daniel
On Jul 8, 2009, at 4:19 PM, "[email protected]"
<[email protected]> wrote:
Author: boisvert
Date: Wed Jul 8 21:19:11 2009
New Revision: 792325
URL: http://svn.apache.org/viewvc?rev=792325&view=rev
Log:
Add example of test:*
Modified:
buildr/trunk/doc/testing.textile
Modified: buildr/trunk/doc/testing.textile
URL:
http://svn.apache.org/viewvc/buildr/trunk/doc/testing.textile?rev=792325&r1=792324&r2=792325&view=diff
===
===
===
=====================================================================
--- buildr/trunk/doc/testing.textile (original)
+++ buildr/trunk/doc/testing.textile Wed Jul 8 21:19:11 2009
@@ -92,6 +92,12 @@
$ buildr test:FooTest,BarTest
{% endhighlight %}
+Buildr forcefully runs all tests that match the pattern. If you
want to re-run all tests even if your sources have not changed, you
can execute:
+
+{% highlight sh %}
+$ buildr test:*
+{% endhighlight %}
+
As you probably noticed, Buildr will stop your build at the first
test that fails. We think it's a good idea, except when it's not.
If you're using a continuous build system, you'll want a report of
all the failed tests without stopping at the first failure. To make
that happen, set the environment variable @test@ to "all", or the
Buildr @options.test@ option to @:a...@. For example:
{% highlight sh %}
