tork 19.11.1 → 20.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/VERSION.markdown +55 -0
- data/bin/tork +1 -1
- data/bin/tork-driver +4 -5
- data/bin/tork-engine +16 -12
- data/bin/tork-herald +1 -1
- data/bin/tork-master +2 -2
- data/bin/tork-notify +3 -3
- data/bin/tork-runner +21 -14
- data/lib/tork/cliapp.rb +22 -18
- data/lib/tork/driver.rb +5 -5
- data/lib/tork/engine.rb +32 -16
- data/lib/tork/master.rb +1 -1
- data/lib/tork/version.rb +1 -1
- data/man/index.html +1 -1
- data/man/man0/README.html +14 -26
- data/man/man0/VERSION.html +148 -93
- data/man/man0/VERSION.markdown +55 -0
- data/man/man1/tork-driver.1 +4 -5
- data/man/man1/tork-driver.1.html +8 -13
- data/man/man1/tork-engine.1 +21 -17
- data/man/man1/tork-engine.1.html +12 -10
- data/man/man1/tork-herald.1 +1 -1
- data/man/man1/tork-herald.1.html +2 -2
- data/man/man1/tork-master.1 +2 -2
- data/man/man1/tork-master.1.html +3 -3
- data/man/man1/tork-notify.1 +1 -1
- data/man/man1/tork-notify.1.html +2 -2
- data/man/man1/tork-remote.1.html +1 -1
- data/man/man1/tork-runner.1 +3 -3
- data/man/man1/tork-runner.1.html +3 -3
- data/man/man1/tork.1 +1 -1
- data/man/man1/tork.1.html +2 -2
- data/man/style.css +1 -1
- data/tork.gemspec +2 -2
- metadata +6 -6
data/man/man0/VERSION.markdown
CHANGED
|
@@ -1,3 +1,58 @@
|
|
|
1
|
+
## Version 20.0.0 (2014-10-26)
|
|
2
|
+
|
|
3
|
+
### Major:
|
|
4
|
+
|
|
5
|
+
* tork-runner(1): percentage lied; print counts instead.
|
|
6
|
+
|
|
7
|
+
The percentage of completion is not accurate because it only measures
|
|
8
|
+
how many tests that have started running _so far_ have been completed.
|
|
9
|
+
This makes the percentage jump from 100% to lesser values as tests run.
|
|
10
|
+
|
|
11
|
+
Also drop the `tork-runner:` prefix from progress messages and replace
|
|
12
|
+
VT100 escape codes for reprinting in-place with a \r (carriage return).
|
|
13
|
+
|
|
14
|
+
* Shorten all status message tokens to ~4 characters.
|
|
15
|
+
|
|
16
|
+
* In tork-driver(1):
|
|
17
|
+
* `reabsorb` is now `over`
|
|
18
|
+
|
|
19
|
+
* In tork-engine(1):
|
|
20
|
+
* `idle` is now `done`
|
|
21
|
+
* `pass_now_fail` is now `fail!`
|
|
22
|
+
* `fail_now_pass` is now `pass!`
|
|
23
|
+
|
|
24
|
+
* In tork-master(1):
|
|
25
|
+
* `absorb` is now `boot`
|
|
26
|
+
|
|
27
|
+
* Shorten all commands names down to ~4 characters.
|
|
28
|
+
|
|
29
|
+
* In tork(1):
|
|
30
|
+
* the `o` input command character is now named `b`
|
|
31
|
+
|
|
32
|
+
* In tork-driver(1):
|
|
33
|
+
* the `run_all_test_files` command is now named `test!`
|
|
34
|
+
* the `over` message is now named `boot!`
|
|
35
|
+
|
|
36
|
+
* In tork-engine(1):
|
|
37
|
+
* the `reabsorb_overhead` command is now named `boot!`
|
|
38
|
+
* the `run_test_file` command is now named `test`
|
|
39
|
+
* the `run_test_files` command is now named `test`
|
|
40
|
+
* the `stop_running_test_files` command is now named `stop`
|
|
41
|
+
* the `rerun_passed_test_files` command is now named `pass!`
|
|
42
|
+
* the `rerun_failed_test_files` command is now named `fail!`
|
|
43
|
+
* the `list_failed_test_files` command is now named `fail?`
|
|
44
|
+
* the `over` status message is now named `boot!`
|
|
45
|
+
|
|
46
|
+
### Minor:
|
|
47
|
+
|
|
48
|
+
* tork-engine(1): add `test?` and `pass?` listing commands.
|
|
49
|
+
|
|
50
|
+
* tork(1): emit "tork:" prefix on all messages sent to user.
|
|
51
|
+
|
|
52
|
+
### Other:
|
|
53
|
+
|
|
54
|
+
* Upgrade to md2man 4.0 and binman 4.0.
|
|
55
|
+
|
|
1
56
|
## Version 19.11.1 (2014-10-24)
|
|
2
57
|
|
|
3
58
|
This release improves support for RSpec 3 and Rails 4.
|
data/man/man1/tork-driver.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH TORK\-DRIVER 1 2014\-10\-
|
|
1
|
+
.TH TORK\-DRIVER 1 2014\-10\-26 20.0.0
|
|
2
2
|
.SH NAME
|
|
3
3
|
.PP
|
|
4
4
|
tork\-driver \- drives
|
|
@@ -28,7 +28,7 @@ of words, using the same word\-splitting algorithm as
|
|
|
28
28
|
before processing
|
|
29
29
|
them. For example, the line \fB\fCa "b c"\fR is split into the \fB\fC["a", "b c"]\fR array.
|
|
30
30
|
.TP
|
|
31
|
-
\fB\fC["
|
|
31
|
+
\fB\fC["test!"]\fR
|
|
32
32
|
Runs all test files found within and beneath the current working directory.
|
|
33
33
|
.TP
|
|
34
34
|
\fI\&...\fP
|
|
@@ -40,9 +40,8 @@ are also accepted here.
|
|
|
40
40
|
This program prints the following messages, which are single\-line JSON arrays,
|
|
41
41
|
to stdout.
|
|
42
42
|
.TP
|
|
43
|
-
\fB\fC["
|
|
44
|
-
|
|
45
|
-
changed.
|
|
43
|
+
\fB\fC["boot!",\fR \fIoverhead_file\fP\fB\fC]\fR
|
|
44
|
+
Reabsorbing test execution overhead because \fIoverhead_file\fP has changed.
|
|
46
45
|
.TP
|
|
47
46
|
\fI\&...\fP
|
|
48
47
|
Messages from
|
data/man/man1/tork-driver.1.html
CHANGED
|
@@ -2,18 +2,17 @@
|
|
|
2
2
|
<html>
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="utf-8" />
|
|
5
|
-
<meta name="generator" content="md2man
|
|
5
|
+
<meta name="generator" content="md2man 4.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="tork-driver-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-driver-1-2014-10-26-20-0-0" href="#tork-driver-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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
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>["
|
|
15
|
-
to stdout.</p><dl><dt><code>["
|
|
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 this Tork process on startup.
|
|
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>["test!"]</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
|
+
to stdout.</p><dl><dt><code>["boot!",</code> <em>overhead_file</em><code>]</code></dt><dd>Reabsorbing test execution overhead because <em>overhead_file</em> has 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 this Tork process on startup.
|
|
17
16
|
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
17
|
It can read and change the following variables.</dd></dl>
|
|
19
18
|
<blockquote>
|
|
@@ -39,8 +38,7 @@ followed by an underscore and the file name in reverse like this:</p>
|
|
|
39
38
|
<li>lib/hello.rb => test/hello_olleh.rb</li>
|
|
40
39
|
<li>app/world.rb => spec/world_ldrow.rb</li>
|
|
41
40
|
</ul>
|
|
42
|
-
<p>Then you would add the following to your configuration file:</p>
|
|
43
|
-
<pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
41
|
+
<p>Then you would add the following to your configuration file:</p><pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
44
42
|
%r{^(lib|app)/.*?([^/]+?)\.rb$} => lambda do |matches|
|
|
45
43
|
name = matches[2]
|
|
46
44
|
"{test,spec}/**/#{name}_#{name.reverse}.rb"
|
|
@@ -55,8 +53,7 @@ prefixed or appended to their already peculiar names, like so:</p>
|
|
|
55
53
|
<li>app/world.rb => spec/world_ldrow_spec.rb</li>
|
|
56
54
|
<li>app/world.rb => spec/spec_world_ldrow.rb</li>
|
|
57
55
|
</ul>
|
|
58
|
-
<p>Then you would add the following to your configuration file:</p>
|
|
59
|
-
<pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
56
|
+
<p>Then you would add the following to your configuration file:</p><pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
60
57
|
%r{^(lib|app)/.*?([^/]+?)\.rb$} => lambda do |matches|
|
|
61
58
|
name = matches[2]
|
|
62
59
|
["{test,spec}/**/#{name}_#{name.reverse}.rb",
|
|
@@ -67,8 +64,7 @@ prefixed or appended to their already peculiar names, like so:</p>
|
|
|
67
64
|
</code></pre>
|
|
68
65
|
<p><strong><em>Recursive expansion</em></strong></p><p>For example, if you wanted to run test files associated with
|
|
69
66
|
<code>lib/hello.rb</code> whenever the <code>app/world.rb</code> file changed, then you would
|
|
70
|
-
write:</p>
|
|
71
|
-
<pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
67
|
+
write:</p><pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
72
68
|
%r{^app/world\.rb$} => lambda do |matches|
|
|
73
69
|
'lib/hello.rb'
|
|
74
70
|
end
|
|
@@ -78,8 +74,7 @@ write:</p>
|
|
|
78
74
|
directions.</p><p><strong><em>Suppressing expansion</em></strong></p><p>These lambda functions can return <code>nil</code> if they do not wish for a
|
|
79
75
|
particular source file to be tested. For example, to ignore tests for
|
|
80
76
|
all source files except those within a <code>models/</code> directory, you would
|
|
81
|
-
write:</p>
|
|
82
|
-
<pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
77
|
+
write:</p><pre><code>Tork::Driver::TEST_FILE_GLOBBERS.update(
|
|
83
78
|
%r{^(lib|app)(/.*?)([^/]+?)\.rb$} => lambda do |matches|
|
|
84
79
|
if matches[2].include? '/models/'
|
|
85
80
|
["{test,spec}/**/#{matches[3]}_{test,spec}.rb",
|
data/man/man1/tork-engine.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH TORK\-ENGINE 1 2014\-10\-
|
|
1
|
+
.TH TORK\-ENGINE 1 2014\-10\-26 20.0.0
|
|
2
2
|
.SH NAME
|
|
3
3
|
.PP
|
|
4
4
|
tork\-engine \- wraps
|
|
@@ -26,30 +26,34 @@ of words, using the same word\-splitting algorithm as
|
|
|
26
26
|
before processing
|
|
27
27
|
them. For example, the line \fB\fCa "b c"\fR is split into the \fB\fC["a", "b c"]\fR array.
|
|
28
28
|
.TP
|
|
29
|
-
\fB\fC["
|
|
29
|
+
\fB\fC["boot!"]\fR
|
|
30
30
|
Stops any test files that are currently running, reabsorbs the test
|
|
31
31
|
execution overhead, and then re\-runs those stopped test files.
|
|
32
|
+
.PP
|
|
33
|
+
\fB\fC["test"\fR, \fItest_file\fP\fB\fC,\fR \fIline_numbers\fP\&...\fB\fC]\fR
|
|
34
|
+
\fB\fC["test"\fR, \fB\fC[\fR\fItest_file\fP\fB\fC,\fR \fIline_numbers\fP\&...\fB\fC]\fR\&...\fB\fC]\fR
|
|
35
|
+
Runs tests that correspond to the given sequence of \fIline_numbers\fP in the
|
|
36
|
+
given \fItest_file\fP\&. If no \fIline_numbers\fP are given, then only those lines
|
|
37
|
+
that have changed since the last run of \fItest_file\fP will be substituted.
|
|
38
|
+
If any \fIline_numbers\fP are zero, then the entire \fItest_file\fP will be run.
|
|
32
39
|
.TP
|
|
33
|
-
\fB\fC["
|
|
34
|
-
|
|
35
|
-
given \fItest_file\fP\&. If no \fIline_numbers\fP are given, then only those lines
|
|
36
|
-
that have changed since the last run of \fItest_file\fP will be substituted.
|
|
37
|
-
If any \fIline_numbers\fP are zero, then the entire \fItest_file\fP will be run.
|
|
38
|
-
.TP
|
|
39
|
-
\fB\fC["run_test_files"\fR, \fItest_files_with_optional_line_numbers\fP\fB\fC]\fR
|
|
40
|
-
Calls the \fB\fCrun_test_file\fR command once for each item in the given array.
|
|
40
|
+
\fB\fC["test?"]\fR
|
|
41
|
+
Lists all test files that are currently running.
|
|
41
42
|
.TP
|
|
42
|
-
\fB\fC["
|
|
43
|
+
\fB\fC["stop"\fR, \fIsignal\fP\fB\fC]\fR
|
|
43
44
|
Stops test files that are currently running by sending the given \fIsignal\fP
|
|
44
45
|
(optional; defaults to "SIGTERM") to their respective worker processes.
|
|
45
46
|
.TP
|
|
46
|
-
\fB\fC["
|
|
47
|
+
\fB\fC["pass!"]\fR
|
|
47
48
|
Runs all test files that have passed during their most recent run.
|
|
48
49
|
.TP
|
|
49
|
-
\fB\fC["
|
|
50
|
+
\fB\fC["pass?"]\fR
|
|
51
|
+
Lists all test files that have passed during their most recent run.
|
|
52
|
+
.TP
|
|
53
|
+
\fB\fC["fail!"]\fR
|
|
50
54
|
Runs all test files that have failed during their most recent run.
|
|
51
55
|
.TP
|
|
52
|
-
\fB\fC["
|
|
56
|
+
\fB\fC["fail?"]\fR
|
|
53
57
|
Lists all test files that have failed during their most recent run.
|
|
54
58
|
.TP
|
|
55
59
|
\fB\fC["quit"]\fR
|
|
@@ -59,15 +63,15 @@ Stops all tests that are currently running and exits.
|
|
|
59
63
|
This program prints the following messages, which are single\-line JSON arrays,
|
|
60
64
|
to stdout.
|
|
61
65
|
.TP
|
|
62
|
-
\fB\fC["
|
|
66
|
+
\fB\fC["done",\fR \fIran\fItest\fPfiles\fP\fB\fC,\fR \fIpassed\fItest\fPfiles\fP\fB\fC,\fR \fIfailed\fItest\fPfiles\fP\fB\fC]\fR
|
|
63
67
|
All queued tests have finished running and no new tests have been queued.
|
|
64
68
|
In particular, \fIran\fItest\fPfiles\fP test files have run, \fIpassed\fItest\fPfiles\fP
|
|
65
69
|
test files have passed, and \fIfailed\fItest\fPfiles\fP test files have failed.
|
|
66
70
|
.TP
|
|
67
|
-
\fB\fC["
|
|
71
|
+
\fB\fC["fail!",\fR \fItest_file\fP\fB\fC,\fR \fImessage\fP\fB\fC]\fR
|
|
68
72
|
A previously passing \fItest_file\fP has now failed. See \fImessage\fP for details.
|
|
69
73
|
.TP
|
|
70
|
-
\fB\fC["
|
|
74
|
+
\fB\fC["pass!",\fR \fItest_file\fP\fB\fC,\fR \fImessage\fP\fB\fC]\fR
|
|
71
75
|
A previously failing \fItest_file\fP has now passed. See \fImessage\fP for details.
|
|
72
76
|
.TP
|
|
73
77
|
\fI\&...\fP
|
data/man/man1/tork-engine.1.html
CHANGED
|
@@ -2,23 +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 4.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="tork-engine-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-engine-1-2014-10-26-20-0-0" href="#tork-engine-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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
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>["
|
|
15
|
-
execution overhead, and then re-runs those stopped test files.</dd></dl><
|
|
16
|
-
|
|
17
|
-
that
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
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>["boot!"]</code></dt><dd>Stops any test files that are currently running, reabsorbs the test
|
|
15
|
+
execution overhead, and then re-runs those stopped test files.</dd></dl><p><code>["test"</code>, <em>test_file</em><code>,</code> <em>line_numbers</em>...<code>]</code>
|
|
16
|
+
<code>["test"</code>, <code>[</code><em>test_file</em><code>,</code> <em>line_numbers</em>...<code>]</code>...<code>]</code>
|
|
17
|
+
Runs tests that correspond to the given sequence of <em>line_numbers</em> in the
|
|
18
|
+
given <em>test_file</em>. If no <em>line_numbers</em> are given, then only those lines
|
|
19
|
+
that have changed since the last run of <em>test_file</em> will be substituted.
|
|
20
|
+
If any <em>line_numbers</em> are zero, then the entire <em>test_file</em> will be run.</p><dl><dt><code>["test?"]</code></dt><dd>Lists all test files that are currently running.</dd></dl><dl><dt><code>["stop"</code>, <em>signal</em><code>]</code></dt><dd>Stops test files that are currently running by sending the given <em>signal</em>
|
|
21
|
+
(optional; defaults to "SIGTERM") to their respective worker processes.</dd></dl><dl><dt><code>["pass!"]</code></dt><dd>Runs all test files that have passed during their most recent run.</dd></dl><dl><dt><code>["pass?"]</code></dt><dd>Lists all test files that have passed during their most recent run.</dd></dl><dl><dt><code>["fail!"]</code></dt><dd>Runs all test files that have failed during their most recent run.</dd></dl><dl><dt><code>["fail?"]</code></dt><dd>Lists 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,
|
|
22
|
+
to stdout.</p><dl><dt><code>["done",</code> <em>ran<em>test</em>files</em><code>,</code> <em>passed<em>test</em>files</em><code>,</code> <em>failed<em>test</em>files</em><code>]</code></dt><dd>All queued tests have finished running and no new tests have been queued.
|
|
21
23
|
In particular, <em>ran<em>test</em>files</em> test files have run, <em>passed<em>test</em>files</em>
|
|
22
|
-
test files have passed, and <em>failed<em>test</em>files</em> test files have failed.</dd></dl><dl><dt><code>["
|
|
24
|
+
test files have passed, and <em>failed<em>test</em>files</em> test files have failed.</dd></dl><dl><dt><code>["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>["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 this Tork process on startup.
|
|
23
25
|
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>
|
|
24
26
|
</html>
|
data/man/man1/tork-herald.1
CHANGED
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 4.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="tork-herald-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-herald-1-2014-10-26-20-0-0" href="#tork-herald-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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
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,4 +1,4 @@
|
|
|
1
|
-
.TH TORK\-MASTER 1 2014\-10\-
|
|
1
|
+
.TH TORK\-MASTER 1 2014\-10\-26 20.0.0
|
|
2
2
|
.SH NAME
|
|
3
3
|
.PP
|
|
4
4
|
tork\-master \- absorbs overhead and runs tests
|
|
@@ -43,7 +43,7 @@ Stops all tests that are currently running and exits.
|
|
|
43
43
|
This program prints the following messages, which are single\-line JSON arrays,
|
|
44
44
|
to stdout.
|
|
45
45
|
.TP
|
|
46
|
-
\fB\fC["
|
|
46
|
+
\fB\fC["boot"]\fR
|
|
47
47
|
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
|
data/man/man1/tork-master.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 4.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="tork-master-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-master-1-2014-10-26-20-0-0" href="#tork-master-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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
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
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,
|
|
@@ -18,7 +18,7 @@ them. For example, the line <code>a "b c"</code> is split into the <c
|
|
|
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
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
|
-
to stdout.</p><dl><dt><code>["
|
|
21
|
+
to stdout.</p><dl><dt><code>["boot"]</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
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 this Tork 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>
|
data/man/man1/tork-notify.1
CHANGED
data/man/man1/tork-notify.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 4.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="tork-notify-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-notify-1-2014-10-26-20-0-0" href="#tork-notify-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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
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
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>
|
data/man/man1/tork-remote.1.html
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
<html>
|
|
3
3
|
<head>
|
|
4
4
|
<meta charset="utf-8" />
|
|
5
|
-
<meta name="generator" content="md2man
|
|
5
|
+
<meta name="generator" content="md2man 4.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]-->
|
data/man/man1/tork-runner.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH TORK\-RUNNER 1 2014\-10\-
|
|
1
|
+
.TH TORK\-RUNNER 1 2014\-10\-26 20.0.0
|
|
2
2
|
.SH NAME
|
|
3
3
|
.PP
|
|
4
4
|
tork\-runner \- runs tests once, non\-interactively
|
|
@@ -26,8 +26,8 @@ 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\
|
|
30
|
-
\
|
|
29
|
+
\fIT\fP \fB\fCtested,\fR \fIP\fP \fB\fCpassed,\fR \fIF\fP \fB\fCfailed\fR
|
|
30
|
+
So far, \fIT\fP test files were tested, \fIP\fP of them passed, \fIF\fP of them failed.
|
|
31
31
|
.SH OPTIONS
|
|
32
32
|
.TP
|
|
33
33
|
\fB\fC\-h\fR, \fB\fC\-\-help\fR
|
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 4.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="tork-runner-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-runner-1-2014-10-26-20-0-0" href="#tork-runner-1-2014-10-26-20-0-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-10-26</span> <span class="md2man-source">20.0.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-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>
|
|
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><em>T</em> <code>tested,</code> <em>P</em> <code>passed,</code> <em>F</em> <code>failed</code></dt><dd>So far, <em>T</em> test files were tested, <em>P</em> of them passed, <em>F</em> of them 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="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
data/man/man1/tork.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 4.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="tork-1-2014-10-
|
|
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-10-26-20-0-0"><a name="tork-1-2014-10-26-20-0-0" href="#tork-1-2014-10-26-20-0-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-10-26</span> <span class="md2man-source">20.0.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
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
|
data/man/style.css
CHANGED
data/tork.gemspec
CHANGED
|
@@ -21,9 +21,9 @@ Gem::Specification.new do |s|
|
|
|
21
21
|
|
|
22
22
|
s.files += Dir['man/man?/*.?'] # UNIX man pages
|
|
23
23
|
s.files += Dir['man/**/*.{html,css,js}'] # HTML man pages
|
|
24
|
-
s.add_development_dependency 'md2man', '~>
|
|
24
|
+
s.add_development_dependency 'md2man', '~> 4.0'
|
|
25
25
|
|
|
26
|
-
s.add_runtime_dependency 'binman', '~>
|
|
26
|
+
s.add_runtime_dependency 'binman', '~> 4.0'
|
|
27
27
|
s.add_runtime_dependency 'json', '~> 1.6'
|
|
28
28
|
s.add_runtime_dependency 'listen', '~> 1.0'
|
|
29
29
|
s.add_runtime_dependency 'diff-lcs', '~> 1.1'
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: tork
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version:
|
|
4
|
+
version: 20.0.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Suraj N. Kurapati
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2014-10-
|
|
12
|
+
date: 2014-10-26 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: md2man
|
|
@@ -17,28 +17,28 @@ dependencies:
|
|
|
17
17
|
requirements:
|
|
18
18
|
- - "~>"
|
|
19
19
|
- !ruby/object:Gem::Version
|
|
20
|
-
version: '
|
|
20
|
+
version: '4.0'
|
|
21
21
|
type: :development
|
|
22
22
|
prerelease: false
|
|
23
23
|
version_requirements: !ruby/object:Gem::Requirement
|
|
24
24
|
requirements:
|
|
25
25
|
- - "~>"
|
|
26
26
|
- !ruby/object:Gem::Version
|
|
27
|
-
version: '
|
|
27
|
+
version: '4.0'
|
|
28
28
|
- !ruby/object:Gem::Dependency
|
|
29
29
|
name: binman
|
|
30
30
|
requirement: !ruby/object:Gem::Requirement
|
|
31
31
|
requirements:
|
|
32
32
|
- - "~>"
|
|
33
33
|
- !ruby/object:Gem::Version
|
|
34
|
-
version: '
|
|
34
|
+
version: '4.0'
|
|
35
35
|
type: :runtime
|
|
36
36
|
prerelease: false
|
|
37
37
|
version_requirements: !ruby/object:Gem::Requirement
|
|
38
38
|
requirements:
|
|
39
39
|
- - "~>"
|
|
40
40
|
- !ruby/object:Gem::Version
|
|
41
|
-
version: '
|
|
41
|
+
version: '4.0'
|
|
42
42
|
- !ruby/object:Gem::Dependency
|
|
43
43
|
name: json
|
|
44
44
|
requirement: !ruby/object:Gem::Requirement
|