tork 19.7.0 → 19.8.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +16 -0
- data/VERSION.md +39 -0
- data/bin/tork +6 -1
- data/bin/tork-driver +1 -1
- data/bin/tork-engine +1 -1
- data/bin/tork-herald +1 -1
- data/bin/tork-master +1 -1
- data/bin/tork-notify +1 -1
- data/bin/tork-remote +1 -1
- data/bin/tork-runner +2 -2
- data/lib/tork/config/bundler/master.rb +2 -0
- data/lib/tork/config/default/config.rb +1 -0
- data/lib/tork/server.rb +1 -1
- data/lib/tork/version.rb +1 -1
- data/man/index.html +1 -1
- data/man/man0/README.html +41 -31
- data/man/man0/README.md +16 -0
- data/man/man0/VERSION.html +233 -201
- data/man/man0/VERSION.md +39 -0
- data/man/man1/tork-driver.1 +4 -4
- data/man/man1/tork-driver.1.html +8 -8
- data/man/man1/tork-engine.1 +3 -3
- data/man/man1/tork-engine.1.html +6 -6
- data/man/man1/tork-herald.1 +3 -3
- data/man/man1/tork-herald.1.html +3 -3
- data/man/man1/tork-master.1 +4 -4
- data/man/man1/tork-master.1.html +8 -8
- data/man/man1/tork-notify.1 +3 -3
- data/man/man1/tork-notify.1.html +4 -4
- data/man/man1/tork-remote.1 +2 -2
- data/man/man1/tork-remote.1.html +3 -3
- data/man/man1/tork-runner.1 +4 -4
- data/man/man1/tork-runner.1.html +3 -3
- data/man/man1/tork.1 +10 -2
- data/man/man1/tork.1.html +9 -8
- data/man/style.css +21 -2
- data/tork.gemspec +1 -1
- metadata +35 -34
data/man/man0/VERSION.md
CHANGED
@@ -1,3 +1,42 @@
|
|
1
|
+
## Version 19.8.0 (2014-06-23)
|
2
|
+
|
3
|
+
### Minor:
|
4
|
+
|
5
|
+
* Add `bundler` configuration helper to load a bundle into tork-master(1).
|
6
|
+
|
7
|
+
This lets you run Tork inside any application that uses Bundler without
|
8
|
+
having to first add Tork to its `Gemfile` and then `bundle install` it.
|
9
|
+
In fact, installing the Tork gem _outside_ of the bundle is sufficient.
|
10
|
+
|
11
|
+
Try it: go into a bundled application and call `tork` to run its tests!
|
12
|
+
|
13
|
+
### Patch:
|
14
|
+
|
15
|
+
* Server: fix crash when Fixnum is sent as a message.
|
16
|
+
|
17
|
+
lib/tork/server.rb:45:in `block (2 levels) in loop':
|
18
|
+
undefined method `empty?' for 6:Fixnum (NoMethodError)
|
19
|
+
|
20
|
+
lib/tork/cliapp.rb:59:in `recv':
|
21
|
+
undefined method `lstrip' for 6:Fixnum (NoMethodError)
|
22
|
+
|
23
|
+
Because JSON.load() and JSON.parse() are different:
|
24
|
+
|
25
|
+
$ irb -r json
|
26
|
+
>> JSON.load '6'
|
27
|
+
6
|
28
|
+
>> JSON.parse '6'
|
29
|
+
JSON::ParserError: A JSON text must at least contain two octets!
|
30
|
+
from /usr/lib/ruby/2.1.0/json/common.rb:155:in `initialize'
|
31
|
+
from /usr/lib/ruby/2.1.0/json/common.rb:155:in `new'
|
32
|
+
from /usr/lib/ruby/2.1.0/json/common.rb:155:in `parse'
|
33
|
+
from (irb):2
|
34
|
+
from /usr/bin/irb:11:in `<main>'
|
35
|
+
|
36
|
+
### Other:
|
37
|
+
|
38
|
+
* Upgrade to md2man 3.0 for improved HTML manuals.
|
39
|
+
|
1
40
|
## Version 19.7.0 (2014-03-04)
|
2
41
|
|
3
42
|
This release automatically re-runs failed tests after reabsorbing overhead.
|
data/man/man1/tork-driver.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-DRIVER 1 2014\-
|
1
|
+
.TH TORK\-DRIVER 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-driver \- drives
|
@@ -6,7 +6,7 @@ tork\-driver \- drives
|
|
6
6
|
when files change
|
7
7
|
.SH SYNOPSIS
|
8
8
|
.PP
|
9
|
-
\fB\fCtork
|
9
|
+
\fB\fCtork\-driver\fR [\fIOPTION\fP]...
|
10
10
|
.SH DESCRIPTION
|
11
11
|
.PP
|
12
12
|
This program drives
|
@@ -52,7 +52,7 @@ and
|
|
52
52
|
are also reproduced here.
|
53
53
|
.SH OPTIONS
|
54
54
|
.TP
|
55
|
-
\fB\fC
|
55
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
56
56
|
Show this help manual.
|
57
57
|
.SH FILES
|
58
58
|
.TP
|
@@ -60,7 +60,7 @@ Show this help manual.
|
|
60
60
|
Optional Ruby script that is loaded inside the driver process on startup.
|
61
61
|
It can read and change the \fB\fCENV['TORK_CONFIGS']\fR environment variable.
|
62
62
|
.TP
|
63
|
-
\fB\fC
|
63
|
+
\fB\fC\&.tork/driver.rb\fR
|
64
64
|
Optional Ruby script that is loaded inside the driver process on startup.
|
65
65
|
It can read and change the following variables.
|
66
66
|
.PP
|
data/man/man1/tork-driver.1.html
CHANGED
@@ -2,25 +2,25 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-driver(1) — drives tork-engine(1) when files change</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-driver-1-2014-06-23-19-8-0" href="#tork-driver-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-DRIVER</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-driver - drives <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a> when files change</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-driver</code> [<em>OPTION</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program drives <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a> when <a class="md2man-reference" 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-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="input"><a name="input" href="#input" class="md2man-permalink" title="permalink"></a>Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
11
11
|
from stdin and then performs the associated actions. For lines read from
|
12
12
|
stdin that are single-line JSON arrays, it splits each of them into an array
|
13
|
-
of words, using the same word-splitting algorithm as <a class="md2man-
|
14
|
-
them. For example, the line <code>a "b c"</code> is split into the <code>["a", "b c"]</code> array.</p><dl><dt><code>["run_all_test_files"]</code></dt><dd>Runs all test files found within and beneath the current working directory.</dd></dl><dl><dt><em>...</em></dt><dd>Commands for <a class="md2man-
|
13
|
+
of words, using the same word-splitting algorithm as <a class="md2man-reference">sh(1)</a>, before processing
|
14
|
+
them. For example, the line <code>a "b c"</code> is split into the <code>["a", "b c"]</code> array.</p><dl><dt><code>["run_all_test_files"]</code></dt><dd>Runs all test files found within and beneath the current working directory.</dd></dl><dl><dt><em>...</em></dt><dd>Commands for <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a> are also accepted here.</dd></dl><h3 id="output"><a name="output" href="#output" class="md2man-permalink" title="permalink"></a>Output</h3><p>This program prints the following messages, which are single-line JSON arrays,
|
15
15
|
to stdout.</p><dl><dt><code>["reabsorb",</code> <em>overhead_file</em><code>]</code></dt><dd>Test execution overhead is being reabsorbed because <em>overhead_file</em> has
|
16
|
-
changed.</dd></dl><dl><dt><em>...</em></dt><dd>Messages from <a class="md2man-
|
16
|
+
changed.</dd></dl><dl><dt><em>...</em></dt><dd>Messages from <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a> and <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a> are also reproduced here.</dd></dl><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="files"><a name="files" href="#files" class="md2man-permalink" title="permalink"></a>FILES</h2><dl><dt><em>.tork/config.rb</em></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
17
17
|
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><dl><dt><code>.tork/driver.rb</code></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
18
18
|
It can read and change the following variables.</dd></dl>
|
19
19
|
<blockquote>
|
20
20
|
<dl><dt><code>Tork::Driver::REABSORB_FILE_GREPS</code></dt><dd>Array of strings or regular expressions that match the paths of overhead
|
21
21
|
files. If any of these equal or match the path of a changed file
|
22
|
-
reported by <a class="md2man-
|
23
|
-
reabsorbed in <a class="md2man-
|
22
|
+
reported by <a class="md2man-reference" href="../man1/tork-herald.1.html">tork-herald(1)</a>, then the test execution overhead will be
|
23
|
+
reabsorbed in <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a>.</dd></dl><dl><dt><code>Tork::Driver::ALL_TEST_FILE_GLOBS</code></dt><dd>Array of file globbing patterns that describe the set of all test files
|
24
24
|
in your Ruby application.</dd></dl><dl><dt><code>Tork::Driver::TEST_FILE_GLOBBERS</code></dt><dd>Hash that maps (1) a regular expression describing a set of file paths
|
25
25
|
to (2) a lambda function that accepts a <code>MatchData</code> object containing
|
26
26
|
the results of the regular expression matching against the path of a
|
@@ -92,5 +92,5 @@ write:</p>
|
|
92
92
|
</code></pre>
|
93
93
|
</blockquote>
|
94
94
|
</blockquote>
|
95
|
-
<h2 id="
|
95
|
+
<h2 id="environment"><a name="environment" href="#environment" class="md2man-permalink" title="permalink"></a>ENVIRONMENT</h2><p>See <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a>, <a class="md2man-reference" href="../man1/tork-herald.1.html">tork-herald(1)</a>, <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a>, <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
96
96
|
</html>
|
data/man/man1/tork-engine.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-ENGINE 1 2014\-
|
1
|
+
.TH TORK\-ENGINE 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-engine \- wraps
|
@@ -6,7 +6,7 @@ tork\-engine \- wraps
|
|
6
6
|
with bookkeeping
|
7
7
|
.SH SYNOPSIS
|
8
8
|
.PP
|
9
|
-
\fB\fCtork
|
9
|
+
\fB\fCtork\-engine\fR [\fIOPTION\fP]...
|
10
10
|
.SH DESCRIPTION
|
11
11
|
.PP
|
12
12
|
This program uses
|
@@ -71,7 +71,7 @@ Messages from
|
|
71
71
|
are also reproduced here.
|
72
72
|
.SH OPTIONS
|
73
73
|
.TP
|
74
|
-
\fB\fC
|
74
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
75
75
|
Show this help manual.
|
76
76
|
.SH FILES
|
77
77
|
.TP
|
data/man/man1/tork-engine.1.html
CHANGED
@@ -2,21 +2,21 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-engine(1) — wraps tork-master(1) with bookkeeping</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-engine-1-2014-06-23-19-8-0" href="#tork-engine-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-ENGINE</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-engine - wraps <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a> with bookkeeping</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-engine</code> [<em>OPTION</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program uses <a class="md2man-reference" 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-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="input"><a name="input" href="#input" class="md2man-permalink" title="permalink"></a>Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
11
11
|
from stdin and then performs the associated actions. For lines read from
|
12
12
|
stdin that are single-line JSON arrays, it splits each of them into an array
|
13
|
-
of words, using the same word-splitting algorithm as <a class="md2man-
|
13
|
+
of words, using the same word-splitting algorithm as <a class="md2man-reference">sh(1)</a>, before processing
|
14
14
|
them. For example, the line <code>a "b c"</code> is split into the <code>["a", "b c"]</code> array.</p><dl><dt><code>["reabsorb_overhead"]</code></dt><dd>Stops any test files that are currently running, reabsorbs the test
|
15
15
|
execution overhead, and then re-runs those stopped test files.</dd></dl><dl><dt><code>["run_test_file"</code>, <em>test_file</em><code>,</code> <em>line_numbers</em>...<code>]</code></dt><dd>Runs tests that correspond to the given sequence of <em>line_numbers</em> in the
|
16
16
|
given <em>test_file</em>. If no <em>line_numbers</em> are given, then only those lines
|
17
17
|
that have changed since the last run of <em>test_file</em> will be substituted.
|
18
18
|
If any <em>line_numbers</em> are zero, then the entire <em>test_file</em> will be run.</dd></dl><dl><dt><code>["run_test_files"</code>, <em>test_files_with_optional_line_numbers</em><code>]</code></dt><dd>Calls the <code>run_test_file</code> command once for each item in the given array.</dd></dl><dl><dt><code>["stop_running_test_files"</code>, <em>signal</em><code>]</code></dt><dd>Stops test files that are currently running by sending the given <em>signal</em>
|
19
|
-
(optional; defaults to "SIGTERM") to their respective worker processes.</dd></dl><dl><dt><code>["rerun_passed_test_files"]</code></dt><dd>Runs all test files that have passed during their most recent run.</dd></dl><dl><dt><code>["rerun_failed_test_files"]</code></dt><dd>Runs all test files that have failed during their most recent run.</dd></dl><dl><dt><code>["quit"]</code></dt><dd>Stops all tests that are currently running and exits.</dd></dl><h3 id="
|
20
|
-
to stdout.</p><dl><dt><code>["idle"]</code></dt><dd>All tests have finished running and no tests are queued for running either.</dd></dl><dl><dt><code>["pass_now_fail",</code> <em>test_file</em><code>,</code> <em>message</em><code>]</code></dt><dd>A previously passing <em>test_file</em> has now failed. See <em>message</em> for details.</dd></dl><dl><dt><code>["fail_now_pass",</code> <em>test_file</em><code>,</code> <em>message</em><code>]</code></dt><dd>A previously failing <em>test_file</em> has now passed. See <em>message</em> for details.</dd></dl><dl><dt><em>...</em></dt><dd>Messages from <a class="md2man-
|
21
|
-
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><dl><dt><em>.tork/engine.rb</em></dt><dd>Optional Ruby script that is loaded inside the master process on startup.</dd></dl><h2 id="
|
19
|
+
(optional; defaults to "SIGTERM") to their respective worker processes.</dd></dl><dl><dt><code>["rerun_passed_test_files"]</code></dt><dd>Runs all test files that have passed during their most recent run.</dd></dl><dl><dt><code>["rerun_failed_test_files"]</code></dt><dd>Runs all test files that have failed during their most recent run.</dd></dl><dl><dt><code>["quit"]</code></dt><dd>Stops all tests that are currently running and exits.</dd></dl><h3 id="output"><a name="output" href="#output" class="md2man-permalink" title="permalink"></a>Output</h3><p>This program prints the following messages, which are single-line JSON arrays,
|
20
|
+
to stdout.</p><dl><dt><code>["idle"]</code></dt><dd>All tests have finished running and no tests are queued for running either.</dd></dl><dl><dt><code>["pass_now_fail",</code> <em>test_file</em><code>,</code> <em>message</em><code>]</code></dt><dd>A previously passing <em>test_file</em> has now failed. See <em>message</em> for details.</dd></dl><dl><dt><code>["fail_now_pass",</code> <em>test_file</em><code>,</code> <em>message</em><code>]</code></dt><dd>A previously failing <em>test_file</em> has now passed. See <em>message</em> for details.</dd></dl><dl><dt><em>...</em></dt><dd>Messages from <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a> are also reproduced here.</dd></dl><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="files"><a name="files" href="#files" class="md2man-permalink" title="permalink"></a>FILES</h2><dl><dt><em>.tork/config.rb</em></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
21
|
+
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><dl><dt><em>.tork/engine.rb</em></dt><dd>Optional Ruby script that is loaded inside the master process on startup.</dd></dl><h2 id="environment"><a name="environment" href="#environment" class="md2man-permalink" title="permalink"></a>ENVIRONMENT</h2><p>See <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a>, <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
22
22
|
</html>
|
data/man/man1/tork-herald.1
CHANGED
@@ -1,10 +1,10 @@
|
|
1
|
-
.TH TORK\-HERALD 1 2014\-
|
1
|
+
.TH TORK\-HERALD 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-herald \- reports modified files
|
5
5
|
.SH SYNOPSIS
|
6
6
|
.PP
|
7
|
-
\fB\fCtork
|
7
|
+
\fB\fCtork\-herald\fR [\fIOPTION\fP]...
|
8
8
|
.SH DESCRIPTION
|
9
9
|
.PP
|
10
10
|
This program monitors the current working directory and all those below it
|
@@ -12,7 +12,7 @@ recursively. When any files therein are modified, it prints their relative
|
|
12
12
|
paths in a single\-line JSON array to stdout.
|
13
13
|
.SH OPTIONS
|
14
14
|
.TP
|
15
|
-
\fB\fC
|
15
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
16
16
|
Show this help manual.
|
17
17
|
.SH SEE ALSO
|
18
18
|
.PP
|
data/man/man1/tork-herald.1.html
CHANGED
@@ -2,12 +2,12 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-herald(1) — reports modified files</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-herald-1-2014-06-23-19-8-0" href="#tork-herald-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-HERALD</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-herald - reports modified files</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-herald</code> [<em>OPTION</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program monitors the current working directory and all those below it
|
11
11
|
recursively. When any files therein are modified, it prints their relative
|
12
|
-
paths in a single-line JSON array to stdout.</p><h2 id="
|
12
|
+
paths in a single-line JSON array to stdout.</p><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>
|
13
13
|
</html>
|
data/man/man1/tork-master.1
CHANGED
@@ -1,10 +1,10 @@
|
|
1
|
-
.TH TORK\-MASTER 1 2014\-
|
1
|
+
.TH TORK\-MASTER 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-master \- absorbs overhead and runs tests
|
5
5
|
.SH SYNOPSIS
|
6
6
|
.PP
|
7
|
-
\fB\fCtork
|
7
|
+
\fB\fCtork\-master\fR [\fIOPTION\fP]...
|
8
8
|
.SH DESCRIPTION
|
9
9
|
.PP
|
10
10
|
This program absorbs your Ruby application's test execution overhead once and
|
@@ -48,7 +48,7 @@ Test execution overhead has been absorbed. We are ready for testing!
|
|
48
48
|
.TP
|
49
49
|
\fB\fC["test",\fR \fItest_file\fP\fB\fC,\fR \fIline_numbers\fP\fB\fC,\fR \fIlog_file\fP\fB\fC,\fR \fIworker_number\fP\fB\fC]\fR
|
50
50
|
Test has begun running. Its output (both stdout and stderr) is being
|
51
|
-
captured into \fIlog_file\fP in real time, so you can watch it with \fB\fCtail
|
51
|
+
captured into \fIlog_file\fP in real time, so you can watch it with \fB\fCtail \-f\fR\&.
|
52
52
|
.TP
|
53
53
|
\fB\fC["pass",\fR \fItest_file\fP\fB\fC,\fR \fIline_numbers\fP\fB\fC,\fR \fIlog_file\fP\fB\fC,\fR \fIworker_number\fP\fB\fC,\fR \fIexit_code\fP\fB\fC,\fR \fIexit_info\fP\fB\fC]\fR
|
54
54
|
Test has passed.
|
@@ -57,7 +57,7 @@ Test has passed.
|
|
57
57
|
Test has failed.
|
58
58
|
.SH OPTIONS
|
59
59
|
.TP
|
60
|
-
\fB\fC
|
60
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
61
61
|
Show this help manual.
|
62
62
|
.SH FILES
|
63
63
|
.TP
|
data/man/man1/tork-master.1.html
CHANGED
@@ -2,24 +2,24 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-master(1) — absorbs overhead and runs tests</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
11
|
-
simply <a class="md2man-
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-master-1-2014-06-23-19-8-0" href="#tork-master-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-MASTER</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-master - absorbs overhead and runs tests</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-master</code> [<em>OPTION</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program absorbs your Ruby application's test execution overhead once and
|
11
|
+
simply <a class="md2man-reference">fork(3)</a>s worker processses to run your tests thereafter. As a result,
|
12
12
|
your tests run faster because they no longer spend any time absorbing the test
|
13
|
-
execution overhead: worker processes simply inherit the overhead when forked.</p><p>This program can be controlled remotely by multiple <a class="md2man-
|
13
|
+
execution overhead: worker processes simply inherit the overhead when forked.</p><p>This program can be controlled remotely by multiple <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="input"><a name="input" href="#input" class="md2man-permalink" title="permalink"></a>Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
14
14
|
from stdin and then performs the associated actions. For lines read from
|
15
15
|
stdin that are single-line JSON arrays, it splits each of them into an array
|
16
|
-
of words, using the same word-splitting algorithm as <a class="md2man-
|
16
|
+
of words, using the same word-splitting algorithm as <a class="md2man-reference">sh(1)</a>, before processing
|
17
17
|
them. For example, the line <code>a "b c"</code> is split into the <code>["a", "b c"]</code> array.</p><dl><dt><code>["test",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>]</code></dt><dd>Forks a worker process to run tests that correspond to the given
|
18
18
|
<em>line_numbers</em> in the given <em>test_file</em>. If <em>line_numbers</em> is empty, then
|
19
19
|
the entire <em>test_file</em> will be run.</dd></dl><dl><dt><code>["stop",</code> <em>signal</em><code>]</code></dt><dd>Stops all tests that are currently running by sending the given <em>signal</em>
|
20
|
-
(optional; defaults to "SIGTERM") to their respective worker processes.</dd></dl><dl><dt><code>["quit"]</code></dt><dd>Stops all tests that are currently running and exits.</dd></dl><h3 id="
|
20
|
+
(optional; defaults to "SIGTERM") to their respective worker processes.</dd></dl><dl><dt><code>["quit"]</code></dt><dd>Stops all tests that are currently running and exits.</dd></dl><h3 id="output"><a name="output" href="#output" class="md2man-permalink" title="permalink"></a>Output</h3><p>This program prints the following messages, which are single-line JSON arrays,
|
21
21
|
to stdout.</p><dl><dt><code>["absorb"]</code></dt><dd>Test execution overhead has been absorbed. We are ready for testing!</dd></dl><dl><dt><code>["test",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>,</code> <em>log_file</em><code>,</code> <em>worker_number</em><code>]</code></dt><dd>Test has begun running. Its output (both stdout and stderr) is being
|
22
|
-
captured into <em>log_file</em> in real time, so you can watch it with <code>tail -f</code>.</dd></dl><dl><dt><code>["pass",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>,</code> <em>log_file</em><code>,</code> <em>worker_number</em><code>,</code> <em>exit_code</em><code>,</code> <em>exit_info</em><code>]</code></dt><dd>Test has passed.</dd></dl><dl><dt><code>["fail",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>,</code> <em>log_file</em><code>,</code> <em>worker_number</em><code>,</code> <em>exit_code</em><code>,</code> <em>exit_info</em><code>]</code></dt><dd>Test has failed.</dd></dl><h2 id="
|
22
|
+
captured into <em>log_file</em> in real time, so you can watch it with <code>tail -f</code>.</dd></dl><dl><dt><code>["pass",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>,</code> <em>log_file</em><code>,</code> <em>worker_number</em><code>,</code> <em>exit_code</em><code>,</code> <em>exit_info</em><code>]</code></dt><dd>Test has passed.</dd></dl><dl><dt><code>["fail",</code> <em>test_file</em><code>,</code> <em>line_numbers</em><code>,</code> <em>log_file</em><code>,</code> <em>worker_number</em><code>,</code> <em>exit_code</em><code>,</code> <em>exit_info</em><code>]</code></dt><dd>Test has failed.</dd></dl><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="files"><a name="files" href="#files" class="md2man-permalink" title="permalink"></a>FILES</h2><dl><dt><em>.tork/config.rb</em></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
23
23
|
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><dl><dt><em>.tork/master.rb</em></dt><dd>Optional Ruby script that is loaded inside the master process on startup.
|
24
24
|
It can read and change the following variables.</dd></dl>
|
25
25
|
<blockquote>
|
@@ -34,5 +34,5 @@ worker process is forked. It can read and change the following variables.</dd><
|
|
34
34
|
it is forked. It can read and change the following variables.</dd></dl>
|
35
35
|
<blockquote>
|
36
36
|
<dl><dt><code>$tork_test_file</code></dt><dd>Path of the test file that will be run by this worker process.</dd></dl><dl><dt><code>$tork_line_numbers</code></dt><dd>Array of line numbers in the test file that were requested to be run.</dd></dl><dl><dt><code>$tork_log_file</code></dt><dd>Path of the log file that will hold the output of this worker process.</dd></dl><dl><dt><code>$tork_worker_number</code></dt><dd>Sequence number of this worker process.</dd></dl></blockquote>
|
37
|
-
<h2 id="
|
37
|
+
<h2 id="environment"><a name="environment" href="#environment" class="md2man-permalink" title="permalink"></a>ENVIRONMENT</h2><p>See <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a></p></div></body>
|
38
38
|
</html>
|
data/man/man1/tork-notify.1
CHANGED
@@ -1,10 +1,10 @@
|
|
1
|
-
.TH TORK\-NOTIFY 1 2014\-
|
1
|
+
.TH TORK\-NOTIFY 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-notify \- notifies you of test status changes
|
5
5
|
.SH SYNOPSIS
|
6
6
|
.PP
|
7
|
-
\fB\fCtork
|
7
|
+
\fB\fCtork\-notify\fR [\fIOPTION\fP]...
|
8
8
|
.SH DESCRIPTION
|
9
9
|
.PP
|
10
10
|
This program serves as an example of how to receive and process messages sent
|
@@ -15,7 +15,7 @@ passing tests fail (or vice versa) through libnotify, xmessage, or growl. If
|
|
15
15
|
none are available on your system, then the notification is printed to stdout.
|
16
16
|
.SH OPTIONS
|
17
17
|
.TP
|
18
|
-
\fB\fC
|
18
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
19
19
|
Show this help manual.
|
20
20
|
.SH EXIT STATUS
|
21
21
|
.PP
|
data/man/man1/tork-notify.1.html
CHANGED
@@ -2,13 +2,13 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-notify(1) — notifies you of test status changes</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
11
|
-
by the various programs in the <a class="md2man-
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-notify-1-2014-06-23-19-8-0" href="#tork-notify-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-NOTIFY</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-notify - notifies you of test status changes</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-notify</code> [<em>OPTION</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program serves as an example of how to receive and process messages sent
|
11
|
+
by the various programs in the <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a> suite. It notifies you when previously
|
12
12
|
passing tests fail (or vice versa) through libnotify, xmessage, or growl. If
|
13
|
-
none are available on your system, then the notification is printed to stdout.</p><h2 id="
|
13
|
+
none are available on your system, then the notification is printed to stdout.</p><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="exit-status"><a name="exit-status" href="#exit-status" class="md2man-permalink" title="permalink"></a>EXIT STATUS</h2><p>See <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a>.</p><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a>, <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a></p></div></body>
|
14
14
|
</html>
|
data/man/man1/tork-remote.1
CHANGED
@@ -6,7 +6,7 @@ tork\-remote \- controls
|
|
6
6
|
programs
|
7
7
|
.SH SYNOPSIS
|
8
8
|
.PP
|
9
|
-
\fB\fCtork
|
9
|
+
\fB\fCtork\-remote\fR [\fIOPTION\fP]... \fIPROGRAM\fP
|
10
10
|
.SH DESCRIPTION
|
11
11
|
.PP
|
12
12
|
This program reads lines from its stdin and sends them to the given \fIPROGRAM\fP,
|
@@ -15,7 +15,7 @@ It also prints lines, received in response, from the given \fIPROGRAM\fP either
|
|
15
15
|
to stdout if they are valid single\-line JSON arrays or to stderr otherwise.
|
16
16
|
.SH OPTIONS
|
17
17
|
.TP
|
18
|
-
\fB\fC
|
18
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
19
19
|
Show this help manual.
|
20
20
|
.SH EXIT STATUS
|
21
21
|
.TP
|
data/man/man1/tork-remote.1.html
CHANGED
@@ -2,13 +2,13 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-remote(1) — controls tork(1) programs</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-remote.1</span></div></div><div class="container-fluid"><h1 id="
|
10
|
+
<body><div class="navbar"><div class="navbar-inner"><span class="brand"><a href="../index.html#man1">man1</a>/tork-remote.1</span></div></div><div class="container-fluid"><h1 id="tork-remote-1-2012-09-26-18-2-3"><a name="tork-remote-1-2012-09-26-18-2-3" href="#tork-remote-1-2012-09-26-18-2-3" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-REMOTE</span> <span class="md2man-section">1</span> <span class="md2man-date">2012-09-26</span> <span class="md2man-source">18.2.3</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-remote - controls <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a> programs</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-remote</code> [<em>OPTION</em>]... <em>PROGRAM</em></p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program reads lines from its stdin and sends them to the given <em>PROGRAM</em>,
|
11
11
|
which must already be running in the same working directory as this program.
|
12
12
|
It also prints lines, received in response, from the given <em>PROGRAM</em> either
|
13
|
-
to stdout if they are valid single-line JSON arrays or to stderr otherwise.</p><h2 id="
|
13
|
+
to stdout if they are valid single-line JSON arrays or to stderr otherwise.</p><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="exit-status"><a name="exit-status" href="#exit-status" class="md2man-permalink" title="permalink"></a>EXIT STATUS</h2><dl><dt>1</dt><dd>Could not connect to the <em>PROGRAM</em>.</dd></dl><dl><dt>2</dt><dd>Lost connection to the <em>PROGRAM</em>.</dd></dl><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-reference" href="../man1/tork-engine.1.html">tork-engine(1)</a>, <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
14
14
|
</html>
|
data/man/man1/tork-runner.1
CHANGED
@@ -1,10 +1,10 @@
|
|
1
|
-
.TH TORK\-RUNNER 1 2014\-
|
1
|
+
.TH TORK\-RUNNER 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-runner \- runs tests once, non\-interactively
|
5
5
|
.SH SYNOPSIS
|
6
6
|
.PP
|
7
|
-
\fB\fCtork
|
7
|
+
\fB\fCtork\-runner\fR [\fIOPTION\fP]... [\fITEST_FILE_GLOB\fP]...
|
8
8
|
.SH DESCRIPTION
|
9
9
|
.PP
|
10
10
|
This program can be thought of as a non\-interactive version of
|
@@ -26,11 +26,11 @@ This message will be followed by the content of \fIfailed_test_log_file\fP\&.
|
|
26
26
|
.PP
|
27
27
|
This program prints the following messages to stderr if it is a TTY device.
|
28
28
|
.TP
|
29
|
-
\fB\fCtork
|
29
|
+
\fB\fCtork\-runner:\fR \fINN.N\fP\fB\fC% tested\fR
|
30
30
|
\fINN.N\fP percent of test files were tested so far.
|
31
31
|
.SH OPTIONS
|
32
32
|
.TP
|
33
|
-
\fB\fC
|
33
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
34
34
|
Show this help manual.
|
35
35
|
.SH EXIT STATUS
|
36
36
|
.TP
|
data/man/man1/tork-runner.1.html
CHANGED
@@ -2,13 +2,13 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork-runner(1) — runs tests once, non-interactively</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-runner-1-2014-06-23-19-8-0" href="#tork-runner-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK-RUNNER</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork-runner - runs tests once, non-interactively</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork-runner</code> [<em>OPTION</em>]... [<em>TEST_FILE_GLOB</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program can be thought of as a non-interactive version of <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>. It
|
11
11
|
runs all test files that match the given <em>TEST_FILE_GLOB</em>s and then exits
|
12
12
|
with a nonzero status if any tests failed. If none are given, it runs all
|
13
|
-
test files known to <code>Tork::Driver::TEST_FILE_GLOBBERS</code> in <a class="md2man-
|
13
|
+
test files known to <code>Tork::Driver::TEST_FILE_GLOBBERS</code> in <a class="md2man-reference" href="../man1/tork-driver.1.html">tork-driver(1)</a>.</p><h3 id="output"><a name="output" href="#output" class="md2man-permalink" title="permalink"></a>Output</h3><p>This program prints the following messages to stdout.</p><dl><dt><code>>></code> <em>failed_test_log_file</em> <code><<</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><p>This program prints the following messages to stderr if it is a TTY device.</p><dl><dt><code>tork-runner:</code> <em>NN.N</em><code>% tested</code></dt><dd><em>NN.N</em> percent of test files were tested so far.</dd></dl><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="exit-status"><a name="exit-status" href="#exit-status" class="md2man-permalink" title="permalink"></a>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"><a name="environment" href="#environment" class="md2man-permalink" title="permalink"></a>ENVIRONMENT</h2><p>See <a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-reference" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>
|
14
14
|
</html>
|
data/man/man1/tork.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK 1 2014\-
|
1
|
+
.TH TORK 1 2014\-06\-23 19.8.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork \- Continuous testing tool for Ruby
|
@@ -39,7 +39,7 @@ This program can be controlled remotely by multiple
|
|
39
39
|
instances.
|
40
40
|
.SH OPTIONS
|
41
41
|
.TP
|
42
|
-
\fB\fC
|
42
|
+
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
43
43
|
Show this help manual.
|
44
44
|
.SH FILES
|
45
45
|
.TP
|
@@ -61,6 +61,8 @@ current working directory appears to utilize what they configure.
|
|
61
61
|
See below for complete descriptions of these configuration helpers.
|
62
62
|
.RS
|
63
63
|
.IP \(bu 2
|
64
|
+
bundler
|
65
|
+
.IP \(bu 2
|
64
66
|
rails
|
65
67
|
.IP \(bu 2
|
66
68
|
devise
|
@@ -113,6 +115,12 @@ testing framework.
|
|
113
115
|
.UE
|
114
116
|
testing framework.
|
115
117
|
.PP
|
118
|
+
\fB\fCbundler\fR
|
119
|
+
Supports the Bundler
|
120
|
+
.UR http://bundler.io
|
121
|
+
.UE
|
122
|
+
dependency framework.
|
123
|
+
.PP
|
116
124
|
\fB\fCrails\fR
|
117
125
|
Supports the Ruby on Rails
|
118
126
|
.UR http://rubyonrails.org
|
data/man/man1/tork.1.html
CHANGED
@@ -2,22 +2,22 @@
|
|
2
2
|
<html>
|
3
3
|
<head>
|
4
4
|
<meta charset="utf-8" />
|
5
|
-
<meta name="generator" content="md2man
|
5
|
+
<meta name="generator" content="md2man 3.0.0 https://github.com/sunaku/md2man" />
|
6
6
|
<title>tork(1) — Continuous testing tool for Ruby</title>
|
7
7
|
<link rel="stylesheet" href="../style.css"/>
|
8
8
|
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
9
9
|
</head>
|
10
|
-
<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="
|
11
|
-
It functions as a rudimentary command-line user interface to <a class="md2man-
|
10
|
+
<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-2014-06-23-19-8-0"><a name="tork-1-2014-06-23-19-8-0" href="#tork-1-2014-06-23-19-8-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-06-23</span> <span class="md2man-source">19.8.0</span></h1><h2 id="name"><a name="name" href="#name" class="md2man-permalink" title="permalink"></a>NAME</h2><p>tork - Continuous testing tool for Ruby</p><h2 id="synopsis"><a name="synopsis" href="#synopsis" class="md2man-permalink" title="permalink"></a>SYNOPSIS</h2><p><code>tork</code> [<em>OPTION</em>]... [<em>CONFIG</em>]...</p><h2 id="description"><a name="description" href="#description" class="md2man-permalink" title="permalink"></a>DESCRIPTION</h2><p>This program can be thought of as an interactive version of <a class="md2man-reference" href="../man1/tork-runner.1.html">tork-runner(1)</a>.
|
11
|
+
It functions as a rudimentary command-line user interface to <a class="md2man-reference" 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
|
12
12
|
directories that contain configuration files or (2) names of configuration
|
13
13
|
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
|
14
|
-
its stdin or (2) remotely through <a class="md2man-
|
14
|
+
its stdin or (2) remotely through <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a>. From then onward, type <code>h</code>
|
15
15
|
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
|
16
16
|
on the given list of <em>line_number</em>s. If no <em>line_number</em>s are given, then
|
17
17
|
only those tests that have changed since the last run of the <em>test_file</em>
|
18
18
|
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>
|
19
|
-
(optional; defaults to <code>SIGTERM</code>) to their respective worker processes.</dd></dl><p>This program can be controlled remotely by multiple <a class="md2man-
|
20
|
-
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><h2 id="
|
19
|
+
(optional; defaults to <code>SIGTERM</code>) to their respective worker processes.</dd></dl><p>This program can be controlled remotely by multiple <a class="md2man-reference" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h2 id="options"><a name="options" href="#options" class="md2man-permalink" title="permalink"></a>OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="files"><a name="files" href="#files" class="md2man-permalink" title="permalink"></a>FILES</h2><dl><dt><em>.tork/config.rb</em></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
20
|
+
It can read and change the <code>ENV['TORK_CONFIGS']</code> environment variable.</dd></dl><h2 id="environment"><a name="environment" href="#environment" class="md2man-permalink" title="permalink"></a>ENVIRONMENT</h2><dl><dt><code>TORK_CONFIGS</code></dt><dd>Colon-separated (:) list of either paths to directories that contain
|
21
21
|
configuration files or names of the following configuration helpers.
|
22
22
|
If this variable is not set, then its value is assumed to be "default".</dd></dl>
|
23
23
|
<blockquote>
|
@@ -25,6 +25,7 @@ If this variable is not set, then its value is assumed to be "default"
|
|
25
25
|
current working directory appears to utilize what they configure.
|
26
26
|
See below for complete descriptions of these configuration helpers.</dd></dl>
|
27
27
|
<ul>
|
28
|
+
<li>bundler</li>
|
28
29
|
<li>rails</li>
|
29
30
|
<li>devise</li>
|
30
31
|
<li>test</li>
|
@@ -38,6 +39,6 @@ was loaded from the current working directory or any of its descendant
|
|
38
39
|
directories (the key) mapped to the following information (the value):</dd></dl>
|
39
40
|
<blockquote>
|
40
41
|
<dl><dt><code>:grade</code></dt><dd>Percentage of source lines that were C0 covered.</dd></dl><dl><dt><code>:nsloc</code></dt><dd>Total number of source lines of code in the file.</dd></dl><dl><dt><code>:holes</code></dt><dd>Line numbers of source lines that were not covered.</dd></dl></blockquote>
|
41
|
-
<dl><dt><code>test</code></dt><dd>Supports the Test::Unit standard library.</dd></dl><dl><dt><code>spec</code></dt><dd>Supports the <a href="http://rspec.info">RSpec</a> testing framework.</dd></dl><dl><dt><code>cucumber</code></dt><dd>Supports the <a href="https://cukes.info">Cucumber</a> testing framework.</dd></dl><dl><dt><code>rails</code></dt><dd>Supports the <a href="http://rubyonrails.org">Ruby on Rails</a> web framework.</dd></dl><dl><dt><code>devise</code></dt><dd>Supports the <a href="https://github.com/plataformatec/devise">Devise</a> authentication framework.</dd></dl><dl><dt><code>factory_girl</code></dt><dd>Supports the <a href="https://github.com/thoughtbot/factory_girl">factory_girl</a> testing library.</dd></dl><dl><dt><code>parallel_tests</code></dt><dd>Supports the <a href="https://github.com/grosser/parallel_tests">parallel_tests</a> testing library.</dd></dl></blockquote>
|
42
|
-
<h2 id="
|
42
|
+
<dl><dt><code>test</code></dt><dd>Supports the Test::Unit standard library.</dd></dl><dl><dt><code>spec</code></dt><dd>Supports the <a href="http://rspec.info">RSpec</a> testing framework.</dd></dl><dl><dt><code>cucumber</code></dt><dd>Supports the <a href="https://cukes.info">Cucumber</a> testing framework.</dd></dl><dl><dt><code>bundler</code></dt><dd>Supports the <a href="http://bundler.io">Bundler</a> dependency framework.</dd></dl><dl><dt><code>rails</code></dt><dd>Supports the <a href="http://rubyonrails.org">Ruby on Rails</a> web framework.</dd></dl><dl><dt><code>devise</code></dt><dd>Supports the <a href="https://github.com/plataformatec/devise">Devise</a> authentication framework.</dd></dl><dl><dt><code>factory_girl</code></dt><dd>Supports the <a href="https://github.com/thoughtbot/factory_girl">factory_girl</a> testing library.</dd></dl><dl><dt><code>parallel_tests</code></dt><dd>Supports the <a href="https://github.com/grosser/parallel_tests">parallel_tests</a> testing library.</dd></dl></blockquote>
|
43
|
+
<h2 id="see-also"><a name="see-also" href="#see-also" class="md2man-permalink" title="permalink"></a>SEE ALSO</h2><p><a class="md2man-reference" href="../man1/tork-runner.1.html">tork-runner(1)</a>, <a class="md2man-reference" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-reference" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
43
44
|
</html>
|