man/man0/README.html in tork-19.4.0 vs man/man0/README.html in tork-19.5.0
- old
+ new
@@ -37,16 +37,17 @@
<h3 id="Architecture">Architecture</h3><p>Following UNIX philosophy, Tork is composed of simple text-based programs that
<em>do one thing well</em>. As a result, you can even create your own user interface
for Tork by wrapping the <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a> program appropriately!</p>
<ul>
<li><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a> is an interactive command-line user interface for <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a></li>
+<li><a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> runs your test suite once, non-interactively, and then exits</li>
<li><a class="md2man-xref" href="../man1/tork-herald.1.html">tork-herald(1)</a> monitors current directory tree and reports changed files</li>
<li><a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a> drives the engine according to the herald's observations</li>
<li><a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> tells master to run tests and keeps track of test results</li>
<li><a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> absorbs test execution overhead and forks to run your tests</li>
<li><a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> remotely controls any Tork program running in the same <code>pwd</code></li>
-<li><a class="md2man-xref" href="../man1/tork-notify.1.html">tork-notify(1)</a> shows how to receive and process messages from Tork programs</li>
+<li><a class="md2man-xref" href="../man1/tork-notify.1.html">tork-notify(1)</a> notifies you when previously passing tests fail or vice versa</li>
</ul>
<p>When the herald observes that files in or beneath the current directory have
been written to, it tells the driver, which then commands the master to fork a
worker process to run the tests affected by those changed files. This is all
performed <em>automatically</em>. However, to run a test file <em>manually</em>, you can:</p>
@@ -68,11 +69,12 @@
# run lines 4, 33, and 21 of test/some_test.rb
echo run_test_file test/some_test.rb 4 33 21 | tork-remote tork-engine
</code></pre></li>
</ol>
-<h2 id="Installation">Installation</h2>
+<p>Alternatively, you can use <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> to run your test suite in one shot
+and then exit with a nonzero status if tests failed, similar to <code>rake test</code>.</p><h2 id="Installation">Installation</h2>
<pre><code>gem install tork
</code></pre>
<h3 id="Prerequisites">Prerequisites</h3>
<ul>
<li><p>Ruby 1.8.7 or 1.9.3 or newer.</p></li>
@@ -108,10 +110,10 @@
<p>You can also do the same non-interactively using a pipeline:</p>
<pre><code># run lines 4, 33, and 21 of test/some_test.rb
echo run_test_file test/some_test.rb 4 33 21 | tork-remote tork-engine
</code></pre>
<p>You can monitor your test processes from another terminal:</p>
-<pre><code>watch 'pgrep -f ^tork | xargs -r ps u'
+<pre><code>watch 'pgrep -f ^tork | xargs -r ps uf'
</code></pre>
<h3 id="With-MiniTest">With MiniTest</h3><p>MiniTest 1.3.2 and newer contain a bug where <code>minitest/autorun</code> won't run any
tests if someone calls <code>Kernel#exit</code> explicitly or simply loads a library
(such as RSpec) which makes the call implicitly. Use Tork 19.0.2+ to avoid
this problem or <a href="https://github.com/seattlerb/minitest/pull/183/files">apply this patch to the minitest library</a> to fix the problem.</p><h3 id="With-RSpec">With RSpec</h3><p>RSpec 2.9.0 and newer contain a bug where RSpec's autorun helper won't run any