tork 19.5.0 → 19.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 36e4aedf556ae64abbcb4145285c543d40d921d6
-  data.tar.gz: db124b05778c46fe798b804bbfc65acf460d4a04
+  metadata.gz: b6d82e539dd5617368961ded0e0108a5b2c13774
+  data.tar.gz: 8f5efa74a17954685684fffeb8a241e4a825aa8a
 SHA512:
-  metadata.gz: eb3c0c1bc467a63a8b65e79fbef2396beb3c639fff4a89d57efd53962095ecc023b45fc2183f77fedb455dfc93d814d263533203a2235fd0af4012fe98d71ce4
-  data.tar.gz: 9471ea8fc915acbb0bce38ac5562dc29ca5924fdee2eb53ef4d9c662ab111ecb2a190cef3c7bbd4d4bd519be633c3e5f1df90b741bbb8a04b6df32370eb73a1c
+  metadata.gz: b7ed16038d95a70c8fb9a0b248bb2f05174991f81ace1f70415a8222e67ca104f1a7e9fd3dd2d1d74da8f2dc0fce47dd56aeb42a67b6f774e4d21098ecc981cc
+  data.tar.gz: df372a4b946764722924c4c289dc566336f40742a2267e3d5838d938af8a3803896dc58cd09a556057b5108f88634d2b6fc7f1a49b720e36bcda0c1b6f01d944

data/README.md

@@ -172,6 +172,10 @@ database adapter][memory_test_fix].  Otherwise, you *might* face these errors:
 
 > cannot start a transaction within a transaction
 
+For older Rails, to use SQLite3 as your test database along with browser-based
+acceptance testing frameworks such as Capybara, see
+http://www.spacevatican.org/2012/8/18/threading-the-rat/
+
 ## Configuration
 
 Tork looks for a configuration directory named `.tork/` inside its working

data/VERSION.md

@@ -1,3 +1,26 @@
+## Version 19.5.1 (2013-12-02)
+
+This release restores support for Capybara integration tests in the `rails`
+configuration helper, corrects the `idle` event in tork-engine(1), and fixes
+some minor bugs in tork-runner(1) and tork(1).
+
+### Patch:
+
+  * Rails: keep sub-Rails connected to in-memory SQLite3 test database.
+
+    When another Rails instance is started by Capybara, it sets up a new
+    connection to the test database instead of re-using our in-memory DB.
+
+    http://www.spacevatican.org/2012/8/18/threading-the-rat/
+
+  * tork-engine(1) sent `idle` event when 1 test was still running.
+
+  * tork-runner(1): prevent Test::Unit from running in `at_exit` hook.
+
+    Test::Unit is finding and running 0 tests in tork-runner(1) itself.
+
+  * tork(1): forgot to update man page: ENTER by itself does nothing now.
+
 ## Version 19.5.0 (2013-11-30)
 
 This release adds a tork-runner(1) program for non-interactive test execution,

data/bin/tork

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK 1 2013-11-30 19.5.0
+# TORK 1 2013-12-02 19.5.1
 
 ## NAME
 
@@ -21,8 +21,8 @@ directories that contain configuration files or (2) names of configuration
 helpers listed in the description of the `TORK_CONFIGS` environment variable.
 
 Next, it waits for you to supply interactive commands either (1) directly on
-its stdin or (2) remotely through tork-remote(1).  From then onward, you may
-press the ENTER key (supplying no command) to see a menu of accepted commands.
+its stdin or (2) remotely through tork-remote(1).  From then onward, type `h`
+and press ENTER to see a help message that shows a menu of accepted commands.
 
 Some interactive commands accept additional arguments, described as follows.
 

data/bin/tork-driver

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-DRIVER 1 2013-11-30 19.5.0
+# TORK-DRIVER 1 2013-12-02 19.5.1
 
 ## NAME
 

data/bin/tork-engine

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-ENGINE 1 2013-11-30 19.5.0
+# TORK-ENGINE 1 2013-12-02 19.5.1
 
 ## NAME
 

data/bin/tork-herald

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-HERALD 1 2013-11-30 19.5.0
+# TORK-HERALD 1 2013-12-02 19.5.1
 
 ## NAME
 

data/bin/tork-master

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-MASTER 1 2013-11-30 19.5.0
+# TORK-MASTER 1 2013-12-02 19.5.1
 
 ## NAME
 

data/bin/tork-notify

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-NOTIFY 1 2013-11-30 19.5.0
+# TORK-NOTIFY 1 2013-12-02 19.5.1
 
 ## NAME
 

data/bin/tork-runner

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 =begin =======================================================================
 
-# TORK-RUNNER 1 2013-11-30 19.5.0
+# TORK-RUNNER 1 2013-12-02 19.5.1
 
 ## NAME
 
@@ -80,7 +80,7 @@ IO.popen('tork-driver', 'w+') do |driver|
     when :idle then
       puts failed.map {|log| [nil, ">> #{log} <<", File.read(log)] }, nil,
            "#{tested} tested, #{passed} passed, #{failed.count} failed"
-      exit failed.empty?
+      exit! failed.empty?
     end
   end
 end

data/lib/tork/config/rails/master.rb

@@ -31,6 +31,14 @@ begin
         if File.exist? seeds = "#{Rails.root}/db/seeds.rb"
           load seeds
         end
+
+        # keep sub-Rails connected to in-memory database
+        # e.g. when another Rails is started by Capybara
+        # http://www.spacevatican.org/2012/8/18/threading-the-rat/
+        class << ActiveRecord::Base
+          memory_database_connection = ActiveRecord::Base.connection
+          define_method(:connection) { memory_database_connection }
+        end
       end
     end
   end

data/lib/tork/engine.rb

@@ -81,12 +81,11 @@ protected
       send @clients, message # propagate downstream
 
       event, file, line_numbers = message
-      case event.to_sym
+      case event_sym = event.to_sym
       when :test
         @queued_test_files.delete file
 
       when :pass
-        finished = true
         # only whole test file runs should qualify as pass
         if line_numbers.empty?
           was_fail = @failed_test_files.delete? file
@@ -95,13 +94,16 @@ protected
         end
 
       when :fail
-        finished = true
         was_pass = @passed_test_files.delete? file
         now_fail = @failed_test_files.add? file
         send @clients, [:pass_now_fail, file, message] if was_pass and now_fail
       end
 
-      send @clients, [:idle] if finished and @queued_test_files.empty?
+      # notify the user when all queued test files have finished running
+      if @queued_test_files.empty? and [:pass, :fail].include? event_sym
+        send @clients, [:idle]
+      end
+
     else
       super
     end

data/lib/tork/version.rb

@@ -1,3 +1,3 @@
 module Tork
-  VERSION = "19.5.0"
+  VERSION = "19.5.1"
 end

data/man/man0/README.html

@@ -131,7 +131,9 @@ specified <code>rails</code> configuration helper has a chance to disable class
 database adapter</a>.  Otherwise, you <em>might</em> face these errors:</p>
 <blockquote>
 <p>SQLite3::BusyException: database is locked</p><p>cannot start a transaction within a transaction</p></blockquote>
-<h2 id="Configuration">Configuration</h2><p>Tork looks for a configuration directory named <code>.tork/</code> inside its working
+<p>For older Rails, to use SQLite3 as your test database along with browser-based
+acceptance testing frameworks such as Capybara, see
+<a href="http://www.spacevatican.org/2012/8/18/threading-the-rat/">http://www.spacevatican.org/2012/8/18/threading-the-rat/</a></p><h2 id="Configuration">Configuration</h2><p>Tork looks for a configuration directory named <code>.tork/</code> inside its working
 directory.  The configuration directory contains specially-named Ruby scripts,
 within which you can query and modify the settings for various tork programs.
 See the &quot;FILES&quot; sections in the manual pages of tork programs for details.</p><p>Note that tork <em>does not</em> automatically reload changes from your configuration

data/man/man0/README.md

@@ -172,6 +172,10 @@ database adapter][memory_test_fix].  Otherwise, you *might* face these errors:
 
 > cannot start a transaction within a transaction
 
+For older Rails, to use SQLite3 as your test database along with browser-based
+acceptance testing frameworks such as Capybara, see
+http://www.spacevatican.org/2012/8/18/threading-the-rat/
+
 ## Configuration
 
 Tork looks for a configuration directory named `.tork/` inside its working

data/man/man0/VERSION.html

@@ -7,7 +7,17 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man0">man0</a>/VERSION</span></div></div><div class="container-fluid"><h2 id="Version-19-5-0-2013-11-30">Version 19.5.0 (2013-11-30)</h2><p>This release adds a <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> program for non-interactive test execution,
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man0">man0</a>/VERSION</span></div></div><div class="container-fluid"><h2 id="Version-19-5-1-2013-12-02">Version 19.5.1 (2013-12-02)</h2><p>This release restores support for Capybara integration tests in the <code>rails</code>
+configuration helper, corrects the <code>idle</code> event in <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a>, and fixes
+some minor bugs in <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> and <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>.</p><h3 id="Patch">Patch:</h3>
+<ul>
+<li><p>Rails: keep sub-Rails connected to in-memory SQLite3 test database.</p><p>When another Rails instance is started by Capybara, it sets up a new
+connection to the test database instead of re-using our in-memory DB.</p><p><a href="http://www.spacevatican.org/2012/8/18/threading-the-rat/">http://www.spacevatican.org/2012/8/18/threading-the-rat/</a></p></li>
+<li><p><a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> sent <code>idle</code> event when 1 test was still running.</p></li>
+<li><p><a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a>: prevent Test::Unit from running in <code>at_exit</code> hook.</p><p>Test::Unit is finding and running 0 tests in <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> itself.</p></li>
+<li><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>: forgot to update man page: ENTER by itself does nothing now.</p></li>
+</ul>
+<h2 id="Version-19-5-0-2013-11-30">Version 19.5.0 (2013-11-30)</h2><p>This release adds a <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a> program for non-interactive test execution,
 makes connections to tork subprocesses self-healing, eliminates &quot;address
 already in use&quot; errors, and fixes bugs in <a class="md2man-xref" href="../man1/tork-herald.1.html">tork-herald(1)</a> and <a class="md2man-xref" href="../man1/tork-notify.1.html">tork-notify(1)</a>.</p><h3 id="Minor">Minor:</h3>
 <ul>

data/man/man0/VERSION.md

@@ -1,3 +1,26 @@
+## Version 19.5.1 (2013-12-02)
+
+This release restores support for Capybara integration tests in the `rails`
+configuration helper, corrects the `idle` event in tork-engine(1), and fixes
+some minor bugs in tork-runner(1) and tork(1).
+
+### Patch:
+
+  * Rails: keep sub-Rails connected to in-memory SQLite3 test database.
+
+    When another Rails instance is started by Capybara, it sets up a new
+    connection to the test database instead of re-using our in-memory DB.
+
+    http://www.spacevatican.org/2012/8/18/threading-the-rat/
+
+  * tork-engine(1) sent `idle` event when 1 test was still running.
+
+  * tork-runner(1): prevent Test::Unit from running in `at_exit` hook.
+
+    Test::Unit is finding and running 0 tests in tork-runner(1) itself.
+
+  * tork(1): forgot to update man page: ENTER by itself does nothing now.
+
 ## Version 19.5.0 (2013-11-30)
 
 This release adds a tork-runner(1) program for non-interactive test execution,

data/man/man1/tork-driver.1

@@ -1,4 +1,4 @@
-.TH TORK\-DRIVER 1 2013\-11\-30 19.5.0
+.TH TORK\-DRIVER 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-driver \- drives 

data/man/man1/tork-driver.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-driver.1</span></div></div><div class="container-fluid"><h1 id="TORK-DRIVER-1-2013-11-30-19-5-0">TORK-DRIVER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-driver - drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when files change</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-driver</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when <a class="md2man-xref" href="../man1/tork-herald.1.html">tork-herald(1)</a> reports files changes.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-driver.1</span></div></div><div class="container-fluid"><h1 id="TORK-DRIVER-1-2013-12-02-19-5-1">TORK-DRIVER 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-driver - drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when files change</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-driver</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when <a class="md2man-xref" href="../man1/tork-herald.1.html">tork-herald(1)</a> reports files changes.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
 from stdin and then performs the associated actions.  For lines read from
 stdin that are single-line JSON arrays, it splits each of them into an array
 of words, using the same word-splitting algorithm as <a class="md2man-xref">sh(1)</a>, before processing

data/man/man1/tork-engine.1

@@ -1,4 +1,4 @@
-.TH TORK\-ENGINE 1 2013\-11\-30 19.5.0
+.TH TORK\-ENGINE 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-engine \- wraps 

data/man/man1/tork-engine.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-engine.1</span></div></div><div class="container-fluid"><h1 id="TORK-ENGINE-1-2013-11-30-19-5-0">TORK-ENGINE 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-engine - wraps <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> with bookkeeping</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-engine</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program uses <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> to run tests and keeps track of the results.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-engine.1</span></div></div><div class="container-fluid"><h1 id="TORK-ENGINE-1-2013-12-02-19-5-1">TORK-ENGINE 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-engine - wraps <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> with bookkeeping</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-engine</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program uses <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> to run tests and keeps track of the results.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
 from stdin and then performs the associated actions.  For lines read from
 stdin that are single-line JSON arrays, it splits each of them into an array
 of words, using the same word-splitting algorithm as <a class="md2man-xref">sh(1)</a>, before processing

data/man/man1/tork-herald.1

@@ -1,4 +1,4 @@
-.TH TORK\-HERALD 1 2013\-11\-30 19.5.0
+.TH TORK\-HERALD 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-herald \- reports modified files

data/man/man1/tork-herald.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-herald.1</span></div></div><div class="container-fluid"><h1 id="TORK-HERALD-1-2013-11-30-19-5-0">TORK-HERALD 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-herald - reports modified files</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-herald</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program monitors the current working directory and all those below it
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-herald.1</span></div></div><div class="container-fluid"><h1 id="TORK-HERALD-1-2013-12-02-19-5-1">TORK-HERALD 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-herald - reports modified files</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-herald</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program monitors the current working directory and all those below it
 recursively.  When any files therein are modified, it prints their relative
 paths in a single-line JSON array to stdout.</p><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>
 </html>

data/man/man1/tork-master.1

@@ -1,4 +1,4 @@
-.TH TORK\-MASTER 1 2013\-11\-30 19.5.0
+.TH TORK\-MASTER 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-master \- absorbs overhead and runs tests

data/man/man1/tork-master.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-master.1</span></div></div><div class="container-fluid"><h1 id="TORK-MASTER-1-2013-11-30-19-5-0">TORK-MASTER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-master - absorbs overhead and runs tests</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-master</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program absorbs your Ruby application&#39;s test execution overhead once and
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-master.1</span></div></div><div class="container-fluid"><h1 id="TORK-MASTER-1-2013-12-02-19-5-1">TORK-MASTER 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-master - absorbs overhead and runs tests</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-master</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program absorbs your Ruby application&#39;s test execution overhead once and
 simply <a class="md2man-xref">fork(3)</a>s worker processses to run your tests thereafter.  As a result,
 your tests run faster because they no longer spend any time absorbing the test
 execution overhead: worker processes simply inherit the overhead when forked.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,

data/man/man1/tork-notify.1

@@ -1,4 +1,4 @@
-.TH TORK\-NOTIFY 1 2013\-11\-30 19.5.0
+.TH TORK\-NOTIFY 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-notify \- notifies you of test status changes

data/man/man1/tork-notify.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-notify.1</span></div></div><div class="container-fluid"><h1 id="TORK-NOTIFY-1-2013-11-30-19-5-0">TORK-NOTIFY 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-notify - notifies you of test status changes</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-notify</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program serves as an example of how to receive and process messages sent
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-notify.1</span></div></div><div class="container-fluid"><h1 id="TORK-NOTIFY-1-2013-12-02-19-5-1">TORK-NOTIFY 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-notify - notifies you of test status changes</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-notify</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program serves as an example of how to receive and process messages sent
 by the various programs in the <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a> suite.  It notifies you when previously
 passing tests fail (or vice versa) through libnotify, xmessage, or growl.  If
 none are available on your system, then the notification is printed to stdout.</p><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><p>See <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>.</p><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>, <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a></p></div></body>

data/man/man1/tork-runner.1

@@ -1,4 +1,4 @@
-.TH TORK\-RUNNER 1 2013\-11\-30 19.5.0
+.TH TORK\-RUNNER 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork\-runner \- runs tests once, non\-interactively

data/man/man1/tork-runner.1.html

@@ -7,7 +7,7 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-runner.1</span></div></div><div class="container-fluid"><h1 id="TORK-RUNNER-1-2013-11-30-19-5-0">TORK-RUNNER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-runner - runs tests once, non-interactively</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-runner</code> [<em>OPTION</em>]... [<em>TEST_FILE_GLOB</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as a non-interactive version of <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>.  It
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-runner.1</span></div></div><div class="container-fluid"><h1 id="TORK-RUNNER-1-2013-12-02-19-5-1">TORK-RUNNER 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork-runner - runs tests once, non-interactively</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-runner</code> [<em>OPTION</em>]... [<em>TEST_FILE_GLOB</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as a non-interactive version of <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>.  It
 runs all test files that match the given <em>TEST_FILE_GLOB</em>s and then exits
 with a nonzero status if any tests failed.  If none are given, it runs all
 test files known to <code>Tork::Driver::TEST_FILE_GLOBBERS</code> in <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>.</p><h3 id="Output">Output</h3><p>This program prints the following messages to stdout.</p><dl><dt><code>&gt;&gt;</code> <em>failed_test_log_file</em> <code>&lt;&lt;</code></dt><dd>This message will be followed by the content of <em>failed_test_log_file</em>.</dd></dl><dl><dt><em>T</em> <code>tested,</code> <em>P</em> <code>passed,</code> <em>F</em> <code>failed</code></dt><dd><em>T</em> test files were tested and <em>P</em> of them passed but <em>F</em> of them failed.</dd></dl><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><dl><dt>0</dt><dd>All test files passed.</dd></dl><dl><dt>1</dt><dd>One or more test files failed.</dd></dl><h2 id="ENVIRONMENT">ENVIRONMENT</h2><p>See <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>

data/man/man1/tork.1

@@ -1,4 +1,4 @@
-.TH TORK 1 2013\-11\-30 19.5.0
+.TH TORK 1 2013\-12\-02 19.5.1
 .SH NAME
 .PP
 tork \- Continuous testing tool for Ruby
@@ -19,8 +19,8 @@ helpers listed in the description of the \fB\fCTORK_CONFIGS\fR environment varia
 Next, it waits for you to supply interactive commands either (1) directly on
 its stdin or (2) remotely through 
 .BR tork-remote (1).  
-From then onward, you may
-press the ENTER key (supplying no command) to see a menu of accepted commands.
+From then onward, type \fB\fCh\fR
+and press ENTER to see a help message that shows a menu of accepted commands.
 .PP
 Some interactive commands accept additional arguments, described as follows.
 .TP

data/man/man1/tork.1.html

@@ -7,12 +7,12 @@
   <link rel="stylesheet" href="../style.css"/>
   <!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
 </head>
-<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork.1</span></div></div><div class="container-fluid"><h1 id="TORK-1-2013-11-30-19-5-0">TORK 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork - Continuous testing tool for Ruby</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork</code> [<em>OPTION</em>]... [<em>CONFIG</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as an interactive version of <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a>.
+<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork.1</span></div></div><div class="container-fluid"><h1 id="TORK-1-2013-12-02-19-5-1">TORK 1 2013-12-02 19.5.1</h1><h2 id="NAME">NAME</h2><p>tork - Continuous testing tool for Ruby</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork</code> [<em>OPTION</em>]... [<em>CONFIG</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as an interactive version of <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a>.
 It functions as a rudimentary command-line user interface to <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>.</p><p>First, it applies the given <em>CONFIG</em> values, which are either (1) paths to
 directories that contain configuration files or (2) names of configuration
 helpers listed in the description of the <code>TORK_CONFIGS</code> environment variable.</p><p>Next, it waits for you to supply interactive commands either (1) directly on
-its stdin or (2) remotely through <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>.  From then onward, you may
-press the ENTER key (supplying no command) to see a menu of accepted commands.</p><p>Some interactive commands accept additional arguments, described as follows.</p><dl><dt><code>t</code> <em>test_file</em> [<em>line_number</em>]...</dt><dd>Runs the given <em>test_file</em> while only running those tests that are defined
+its stdin or (2) remotely through <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>.  From then onward, type <code>h</code>
+and press ENTER to see a help message that shows a menu of accepted commands.</p><p>Some interactive commands accept additional arguments, described as follows.</p><dl><dt><code>t</code> <em>test_file</em> [<em>line_number</em>]...</dt><dd>Runs the given <em>test_file</em> while only running those tests that are defined
 on the given list of <em>line_number</em>s.  If no <em>line_number</em>s are given, then
 only those tests that have changed since the last run of the <em>test_file</em>
 will now be run.</dd></dl><dl><dt><code>s</code> [<em>signal</em>]</dt><dd>Stops test files that are currently running by sending the given <em>signal</em>

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: tork
 version: !ruby/object:Gem::Version
-  version: 19.5.0
+  version: 19.5.1
 platform: ruby
 authors:
 - Suraj N. Kurapati
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-11-30 00:00:00.000000000 Z
+date: 2013-12-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: md2man