tork 19.4.0 → 19.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +6 -2
- data/VERSION.md +191 -102
- data/bin/tork +4 -3
- data/bin/tork-driver +5 -2
- data/bin/tork-engine +5 -2
- data/bin/tork-herald +3 -3
- data/bin/tork-master +5 -2
- data/bin/tork-notify +3 -2
- data/bin/tork-remote +4 -9
- data/bin/tork-runner +86 -0
- data/lib/tork/bridge.rb +66 -0
- data/lib/tork/cliapp.rb +21 -13
- data/lib/tork/config/rails/worker.rb +1 -1
- data/lib/tork/engine.rb +3 -12
- data/lib/tork/server.rb +31 -37
- data/lib/tork/version.rb +1 -1
- data/man/index.html +1 -1
- data/man/man0/README.html +5 -3
- data/man/man0/README.md +6 -2
- data/man/man0/VERSION.html +156 -102
- data/man/man0/VERSION.md +191 -102
- data/man/man1/tork-driver.1 +7 -2
- data/man/man1/tork-driver.1.html +5 -2
- data/man/man1/tork-engine.1 +7 -2
- data/man/man1/tork-engine.1.html +5 -2
- data/man/man1/tork-herald.1 +1 -1
- data/man/man1/tork-herald.1.html +1 -1
- data/man/man1/tork-master.1 +7 -2
- data/man/man1/tork-master.1.html +5 -2
- data/man/man1/tork-notify.1 +1 -1
- data/man/man1/tork-notify.1.html +1 -1
- data/man/man1/tork-remote.1 +4 -10
- data/man/man1/tork-remote.1.html +4 -5
- data/man/man1/tork-runner.1 +44 -0
- data/man/man1/tork-runner.1.html +14 -0
- data/man/man1/tork.1 +5 -3
- data/man/man1/tork.1.html +3 -2
- data/man/style.css +1 -1
- data/tork.gemspec +2 -1
- metadata +11 -5
data/man/man1/tork-driver.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-DRIVER 1 2013\-11\-
|
1
|
+
.TH TORK\-DRIVER 1 2013\-11\-30 19.5.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-driver \- drives
|
@@ -21,7 +21,12 @@ instances.
|
|
21
21
|
.SS Input
|
22
22
|
.PP
|
23
23
|
This program reads the following commands, which are single\-line JSON arrays,
|
24
|
-
from stdin and performs the actions
|
24
|
+
from stdin and then performs the associated actions. For lines read from
|
25
|
+
stdin that are single\-line JSON arrays, it splits each of them into an array
|
26
|
+
of words, using the same word\-splitting algorithm as
|
27
|
+
.BR sh (1),
|
28
|
+
before processing
|
29
|
+
them. For example, the line \fB\fCa "b c"\fR is split into the \fB\fC["a", "b c"]\fR array.
|
25
30
|
.TP
|
26
31
|
\fB\fC["run_all_test_files"]\fR
|
27
32
|
Runs all test files found within and beneath the current working directory.
|
data/man/man1/tork-driver.1.html
CHANGED
@@ -7,8 +7,11 @@
|
|
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-2013-11-
|
11
|
-
from stdin and performs the actions
|
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-2013-11-30-19-5-0">TORK-DRIVER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-driver - drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when files change</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-driver</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program drives <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> when <a class="md2man-xref" href="../man1/tork-herald.1.html">tork-herald(1)</a> reports files changes.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
11
|
+
from stdin and then performs the associated actions. For lines read from
|
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-xref">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-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> are also accepted here.</dd></dl><h3 id="Output">Output</h3><p>This program prints the following messages, which are single-line JSON arrays,
|
12
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
|
13
16
|
changed.</dd></dl><dl><dt><em>...</em></dt><dd>Messages from <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a> and <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> are also reproduced here.</dd></dl><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="FILES">FILES</h2><dl><dt><em>.tork/config.rb</em></dt><dd>Optional Ruby script that is loaded inside the driver process on startup.
|
14
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.
|
data/man/man1/tork-engine.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-ENGINE 1 2013\-11\-
|
1
|
+
.TH TORK\-ENGINE 1 2013\-11\-30 19.5.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-engine \- wraps
|
@@ -19,7 +19,12 @@ instances.
|
|
19
19
|
.SS Input
|
20
20
|
.PP
|
21
21
|
This program reads the following commands, which are single\-line JSON arrays,
|
22
|
-
from stdin and performs the actions
|
22
|
+
from stdin and then performs the associated actions. For lines read from
|
23
|
+
stdin that are single\-line JSON arrays, it splits each of them into an array
|
24
|
+
of words, using the same word\-splitting algorithm as
|
25
|
+
.BR sh (1),
|
26
|
+
before processing
|
27
|
+
them. For example, the line \fB\fCa "b c"\fR is split into the \fB\fC["a", "b c"]\fR array.
|
23
28
|
.TP
|
24
29
|
\fB\fC["reabsorb_overhead"]\fR
|
25
30
|
Stops any test files that are currently running, reabsorbs the test
|
data/man/man1/tork-engine.1.html
CHANGED
@@ -7,8 +7,11 @@
|
|
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-2013-11-
|
11
|
-
from stdin and performs the actions
|
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-2013-11-30-19-5-0">TORK-ENGINE 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-engine - wraps <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> with bookkeeping</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-engine</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program uses <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a> to run tests and keeps track of the results.</p><p>This program can be controlled remotely by multiple <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
11
|
+
from stdin and then performs the associated actions. For lines read from
|
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-xref">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>["reabsorb_overhead"]</code></dt><dd>Stops any test files that are currently running, reabsorbs the test
|
12
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
|
13
16
|
given <em>test_file</em>. If no <em>line_numbers</em> are given, then only those lines
|
14
17
|
that have changed since the last run of <em>test_file</em> will be substituted.
|
data/man/man1/tork-herald.1
CHANGED
data/man/man1/tork-herald.1.html
CHANGED
@@ -7,7 +7,7 @@
|
|
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-2013-11-
|
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-2013-11-30-19-5-0">TORK-HERALD 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-herald - reports modified files</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-herald</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program monitors the current working directory and all those below it
|
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">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>
|
13
13
|
</html>
|
data/man/man1/tork-master.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-MASTER 1 2013\-11\-
|
1
|
+
.TH TORK\-MASTER 1 2013\-11\-30 19.5.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-master \- absorbs overhead and runs tests
|
@@ -20,7 +20,12 @@ instances.
|
|
20
20
|
.SS Input
|
21
21
|
.PP
|
22
22
|
This program reads the following commands, which are single\-line JSON arrays,
|
23
|
-
from stdin and performs the actions
|
23
|
+
from stdin and then performs the associated actions. For lines read from
|
24
|
+
stdin that are single\-line JSON arrays, it splits each of them into an array
|
25
|
+
of words, using the same word\-splitting algorithm as
|
26
|
+
.BR sh (1),
|
27
|
+
before processing
|
28
|
+
them. For example, the line \fB\fCa "b c"\fR is split into the \fB\fC["a", "b c"]\fR array.
|
24
29
|
.TP
|
25
30
|
\fB\fC["test",\fR \fItest_file\fP\fB\fC,\fR \fIline_numbers\fP\fB\fC]\fR
|
26
31
|
Forks a worker process to run tests that correspond to the given
|
data/man/man1/tork-master.1.html
CHANGED
@@ -7,11 +7,14 @@
|
|
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-2013-11-
|
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-2013-11-30-19-5-0">TORK-MASTER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-master - absorbs overhead and runs tests</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-master</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program absorbs your Ruby application's test execution overhead once and
|
11
11
|
simply <a class="md2man-xref">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-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a> instances.</p><h3 id="Input">Input</h3><p>This program reads the following commands, which are single-line JSON arrays,
|
14
|
-
from stdin and performs the actions
|
14
|
+
from stdin and then performs the associated actions. For lines read from
|
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-xref">sh(1)</a>, before processing
|
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
|
15
18
|
<em>line_numbers</em> in the given <em>test_file</em>. If <em>line_numbers</em> is empty, then
|
16
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>
|
17
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">Output</h3><p>This program prints the following messages, which are single-line JSON arrays,
|
data/man/man1/tork-notify.1
CHANGED
data/man/man1/tork-notify.1.html
CHANGED
@@ -7,7 +7,7 @@
|
|
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-2013-11-
|
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-2013-11-30-19-5-0">TORK-NOTIFY 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-notify - notifies you of test status changes</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-notify</code> [<em>OPTION</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program serves as an example of how to receive and process messages sent
|
11
11
|
by the various programs in the <a class="md2man-xref" 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">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><p>See <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>.</p><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>, <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a></p></div></body>
|
data/man/man1/tork-remote.1
CHANGED
@@ -9,16 +9,10 @@ programs
|
|
9
9
|
\fB\fCtork-remote\fR [\fIOPTION\fP]... \fIPROGRAM\fP
|
10
10
|
.SH DESCRIPTION
|
11
11
|
.PP
|
12
|
-
This program
|
13
|
-
|
14
|
-
|
15
|
-
|
16
|
-
split into an array of words, using the same word\-splitting algorithm as
|
17
|
-
.BR sh (1),
|
18
|
-
before being sent to the \fIPROGRAM\fP as a single\-line JSON message.
|
19
|
-
.PP
|
20
|
-
If the \fIPROGRAM\fP sends any messages in response, then they are printed to
|
21
|
-
stdout if they are valid single\-line JSON messages or to stderr otherwise.
|
12
|
+
This program reads lines from its stdin and sends them to the given \fIPROGRAM\fP,
|
13
|
+
which must already be running in the same working directory as this program.
|
14
|
+
It also prints lines, received in response, from the given \fIPROGRAM\fP either
|
15
|
+
to stdout if they are valid single\-line JSON arrays or to stderr otherwise.
|
22
16
|
.SH OPTIONS
|
23
17
|
.TP
|
24
18
|
\fB\fC-h\fR, \fB\fC--help\fR
|
data/man/man1/tork-remote.1.html
CHANGED
@@ -7,9 +7,8 @@
|
|
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="TORK-REMOTE-1-2012-09-26-18-2-3">TORK-REMOTE 1 2012-09-26 18.2.3</h1><h2 id="NAME">NAME</h2><p>tork-remote - controls <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a> programs</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-remote</code> [<em>OPTION</em>]... <em>PROGRAM</em></p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program
|
11
|
-
|
12
|
-
|
13
|
-
<
|
14
|
-
stdout if they are valid single-line JSON messages or to stderr otherwise.</p><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><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">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a>, <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
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">TORK-REMOTE 1 2012-09-26 18.2.3</h1><h2 id="NAME">NAME</h2><p>tork-remote - controls <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a> programs</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-remote</code> [<em>OPTION</em>]... <em>PROGRAM</em></p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program reads lines from its stdin and sends them to the given <em>PROGRAM</em>,
|
11
|
+
which must already be running in the same working directory as this program.
|
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="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><dl><dt>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">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-xref" href="../man1/tork-engine.1.html">tork-engine(1)</a>, <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
15
14
|
</html>
|
@@ -0,0 +1,44 @@
|
|
1
|
+
.TH TORK\-RUNNER 1 2013\-11\-30 19.5.0
|
2
|
+
.SH NAME
|
3
|
+
.PP
|
4
|
+
tork\-runner \- runs tests once, non\-interactively
|
5
|
+
.SH SYNOPSIS
|
6
|
+
.PP
|
7
|
+
\fB\fCtork-runner\fR [\fIOPTION\fP]... [\fITEST_FILE_GLOB\fP]...
|
8
|
+
.SH DESCRIPTION
|
9
|
+
.PP
|
10
|
+
This program can be thought of as a non\-interactive version of
|
11
|
+
.BR tork (1).
|
12
|
+
It
|
13
|
+
runs all test files that match the given \fITEST_FILE_GLOB\fPs and then exits
|
14
|
+
with a nonzero status if any tests failed. If none are given, it runs all
|
15
|
+
test files known to \fB\fCTork::Driver::TEST_FILE_GLOBBERS\fR in
|
16
|
+
.BR tork-driver (1).
|
17
|
+
.SS Output
|
18
|
+
.PP
|
19
|
+
This program prints the following messages to stdout.
|
20
|
+
.TP
|
21
|
+
\fB\fC>>\fR \fIfailed_test_log_file\fP \fB\fC<<\fR
|
22
|
+
This message will be followed by the content of \fIfailed_test_log_file\fP\&.
|
23
|
+
.TP
|
24
|
+
\fIT\fP \fB\fCtested,\fR \fIP\fP \fB\fCpassed,\fR \fIF\fP \fB\fCfailed\fR
|
25
|
+
\fIT\fP test files were tested and \fIP\fP of them passed but \fIF\fP of them failed.
|
26
|
+
.SH OPTIONS
|
27
|
+
.TP
|
28
|
+
\fB\fC-h\fR, \fB\fC--help\fR
|
29
|
+
Show this help manual.
|
30
|
+
.SH EXIT STATUS
|
31
|
+
.TP
|
32
|
+
0
|
33
|
+
All test files passed.
|
34
|
+
.TP
|
35
|
+
1
|
36
|
+
One or more test files failed.
|
37
|
+
.SH ENVIRONMENT
|
38
|
+
.PP
|
39
|
+
See
|
40
|
+
.BR tork (1).
|
41
|
+
.SH SEE ALSO
|
42
|
+
.PP
|
43
|
+
.BR tork (1),
|
44
|
+
.BR tork-driver (1)
|
@@ -0,0 +1,14 @@
|
|
1
|
+
<!DOCTYPE html>
|
2
|
+
<html>
|
3
|
+
<head>
|
4
|
+
<meta charset="utf-8" />
|
5
|
+
<meta name="generator" content="md2man 2.0.2 https://github.com/sunaku/md2man" />
|
6
|
+
<title>tork-runner(1) — runs tests once, non-interactively</title>
|
7
|
+
<link rel="stylesheet" href="../style.css"/>
|
8
|
+
<!--[if lt IE 9]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
|
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-2013-11-30-19-5-0">TORK-RUNNER 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork-runner - runs tests once, non-interactively</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork-runner</code> [<em>OPTION</em>]... [<em>TEST_FILE_GLOB</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as a non-interactive version of <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>. It
|
11
|
+
runs all test files that match the given <em>TEST_FILE_GLOB</em>s and then exits
|
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-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>.</p><h3 id="Output">Output</h3><p>This program prints the following messages to stdout.</p><dl><dt><code>>></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><h2 id="OPTIONS">OPTIONS</h2><dl><dt><code>-h</code>, <code>--help</code></dt><dd>Show this help manual.</dd></dl><h2 id="EXIT-STATUS">EXIT STATUS</h2><dl><dt>0</dt><dd>All test files passed.</dd></dl><dl><dt>1</dt><dd>One or more test files failed.</dd></dl><h2 id="ENVIRONMENT">ENVIRONMENT</h2><p>See <a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>.</p><h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a></p></div></body>
|
14
|
+
</html>
|
data/man/man1/tork.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK 1 2013\-11\-
|
1
|
+
.TH TORK 1 2013\-11\-30 19.5.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork \- Continuous testing tool for Ruby
|
@@ -7,7 +7,9 @@ tork \- Continuous testing tool for Ruby
|
|
7
7
|
\fB\fCtork\fR [\fIOPTION\fP]... [\fICONFIG\fP]...
|
8
8
|
.SH DESCRIPTION
|
9
9
|
.PP
|
10
|
-
This program
|
10
|
+
This program can be thought of as an interactive version of
|
11
|
+
.BR tork-runner (1).
|
12
|
+
It functions as a rudimentary command\-line user interface to
|
11
13
|
.BR tork-driver (1).
|
12
14
|
.PP
|
13
15
|
First, it applies the given \fICONFIG\fP values, which are either (1) paths to
|
@@ -137,6 +139,6 @@ testing library.
|
|
137
139
|
.RE
|
138
140
|
.SH SEE ALSO
|
139
141
|
.PP
|
140
|
-
.BR tork (1),
|
142
|
+
.BR tork-runner (1),
|
141
143
|
.BR tork-driver (1),
|
142
144
|
.BR tork-master (1)
|
data/man/man1/tork.1.html
CHANGED
@@ -7,7 +7,8 @@
|
|
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-2013-11-
|
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-2013-11-30-19-5-0">TORK 1 2013-11-30 19.5.0</h1><h2 id="NAME">NAME</h2><p>tork - Continuous testing tool for Ruby</p><h2 id="SYNOPSIS">SYNOPSIS</h2><p><code>tork</code> [<em>OPTION</em>]... [<em>CONFIG</em>]...</p><h2 id="DESCRIPTION">DESCRIPTION</h2><p>This program can be thought of as an interactive version of <a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a>.
|
11
|
+
It functions as a rudimentary command-line user interface to <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>.</p><p>First, it applies the given <em>CONFIG</em> values, which are either (1) paths to
|
11
12
|
directories that contain configuration files or (2) names of configuration
|
12
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
|
13
14
|
its stdin or (2) remotely through <a class="md2man-xref" href="../man1/tork-remote.1.html">tork-remote(1)</a>. From then onward, you may
|
@@ -38,5 +39,5 @@ directories (the key) mapped to the following information (the value):</dd></dl>
|
|
38
39
|
<blockquote>
|
39
40
|
<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>
|
40
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>
|
41
|
-
<h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork.1.html">tork(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
42
|
+
<h2 id="SEE-ALSO">SEE ALSO</h2><p><a class="md2man-xref" href="../man1/tork-runner.1.html">tork-runner(1)</a>, <a class="md2man-xref" href="../man1/tork-driver.1.html">tork-driver(1)</a>, <a class="md2man-xref" href="../man1/tork-master.1.html">tork-master(1)</a></p></div></body>
|
42
43
|
</html>
|
data/man/style.css
CHANGED
data/tork.gemspec
CHANGED
@@ -12,6 +12,7 @@ Gem::Specification.new do |s|
|
|
12
12
|
s.homepage = 'http://github.com/sunaku/tork'
|
13
13
|
s.summary = 'test with fork'
|
14
14
|
s.description = 'Runs your tests as they change, in parallel.'
|
15
|
+
s.license = 'ISC'
|
15
16
|
|
16
17
|
s.files = `git ls-files`.split("\n")
|
17
18
|
s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
|
@@ -24,7 +25,7 @@ Gem::Specification.new do |s|
|
|
24
25
|
|
25
26
|
s.add_runtime_dependency 'binman', '~> 3.0'
|
26
27
|
s.add_runtime_dependency 'json', '~> 1.6'
|
27
|
-
s.add_runtime_dependency 'listen', '~>
|
28
|
+
s.add_runtime_dependency 'listen', '~> 1.0'
|
28
29
|
s.add_runtime_dependency 'diff-lcs', '~> 1.1'
|
29
30
|
s.add_development_dependency 'rake', '~> 10.0'
|
30
31
|
end
|
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: 19.
|
4
|
+
version: 19.5.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: 2013-11-
|
12
|
+
date: 2013-11-30 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: md2man
|
@@ -59,14 +59,14 @@ dependencies:
|
|
59
59
|
requirements:
|
60
60
|
- - ~>
|
61
61
|
- !ruby/object:Gem::Version
|
62
|
-
version: '
|
62
|
+
version: '1.0'
|
63
63
|
type: :runtime
|
64
64
|
prerelease: false
|
65
65
|
version_requirements: !ruby/object:Gem::Requirement
|
66
66
|
requirements:
|
67
67
|
- - ~>
|
68
68
|
- !ruby/object:Gem::Version
|
69
|
-
version: '
|
69
|
+
version: '1.0'
|
70
70
|
- !ruby/object:Gem::Dependency
|
71
71
|
name: diff-lcs
|
72
72
|
requirement: !ruby/object:Gem::Requirement
|
@@ -107,6 +107,7 @@ executables:
|
|
107
107
|
- tork-master
|
108
108
|
- tork-notify
|
109
109
|
- tork-remote
|
110
|
+
- tork-runner
|
110
111
|
extensions: []
|
111
112
|
extra_rdoc_files: []
|
112
113
|
files:
|
@@ -123,6 +124,8 @@ files:
|
|
123
124
|
- bin/tork-master
|
124
125
|
- bin/tork-notify
|
125
126
|
- bin/tork-remote
|
127
|
+
- bin/tork-runner
|
128
|
+
- lib/tork/bridge.rb
|
126
129
|
- lib/tork/cliapp.rb
|
127
130
|
- lib/tork/config.rb
|
128
131
|
- lib/tork/config/coverage/master.rb
|
@@ -161,10 +164,12 @@ files:
|
|
161
164
|
- man/man1/tork-notify.1
|
162
165
|
- man/man1/tork-driver.1
|
163
166
|
- man/man1/tork.1
|
167
|
+
- man/man1/tork-runner.1
|
164
168
|
- man/index.html
|
165
169
|
- man/man1/tork-notify.1.html
|
166
170
|
- man/man1/tork-herald.1.html
|
167
171
|
- man/man1/tork-master.1.html
|
172
|
+
- man/man1/tork-runner.1.html
|
168
173
|
- man/man1/tork.1.html
|
169
174
|
- man/man1/tork-engine.1.html
|
170
175
|
- man/man1/tork-driver.1.html
|
@@ -173,7 +178,8 @@ files:
|
|
173
178
|
- man/man0/README.html
|
174
179
|
- man/style.css
|
175
180
|
homepage: http://github.com/sunaku/tork
|
176
|
-
licenses:
|
181
|
+
licenses:
|
182
|
+
- ISC
|
177
183
|
metadata: {}
|
178
184
|
post_install_message:
|
179
185
|
rdoc_options: []
|