tork 19.9.0 → 19.10.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 +31 -0
- data/bin/tork +1 -1
- data/bin/tork-driver +1 -1
- data/bin/tork-engine +8 -3
- data/bin/tork-herald +1 -1
- data/bin/tork-master +1 -1
- data/bin/tork-notify +1 -1
- data/bin/tork-runner +1 -1
- data/lib/tork/cliapp.rb +10 -4
- data/lib/tork/config.rb +6 -1
- data/lib/tork/config/bundler/{config.rb → detect.rb} +0 -0
- data/lib/tork/config/cucumber/{config.rb → detect.rb} +0 -0
- data/lib/tork/config/devise/{config.rb → detect.rb} +0 -0
- data/lib/tork/config/factory_girl/{config.rb → detect.rb} +0 -0
- data/lib/tork/config/rails/{config.rb → detect.rb} +0 -0
- data/lib/tork/config/spec/config.rb +0 -2
- data/lib/tork/config/spec/detect.rb +1 -0
- data/lib/tork/config/test/config.rb +0 -2
- data/lib/tork/config/test/detect.rb +1 -0
- data/lib/tork/driver.rb +7 -6
- data/lib/tork/engine.rb +27 -6
- data/lib/tork/version.rb +1 -1
- data/man/man0/VERSION.html +128 -107
- data/man/man0/VERSION.markdown +31 -0
- data/man/man1/tork-driver.1 +1 -1
- data/man/man1/tork-driver.1.html +1 -1
- data/man/man1/tork-engine.1 +8 -3
- data/man/man1/tork-engine.1.html +5 -3
- data/man/man1/tork-herald.1 +1 -1
- data/man/man1/tork-herald.1.html +1 -1
- data/man/man1/tork-master.1 +1 -1
- data/man/man1/tork-master.1.html +1 -1
- data/man/man1/tork-notify.1 +1 -1
- data/man/man1/tork-notify.1.html +1 -1
- data/man/man1/tork-runner.1 +1 -1
- data/man/man1/tork-runner.1.html +1 -1
- data/man/man1/tork.1 +1 -1
- data/man/man1/tork.1.html +1 -1
- metadata +9 -7
data/man/man0/VERSION.markdown
CHANGED
@@ -1,3 +1,34 @@
|
|
1
|
+
## Version 19.10.0 (2014-08-06)
|
2
|
+
|
3
|
+
This release improves responsiveness and adds a command to list failed files.
|
4
|
+
|
5
|
+
### Minor:
|
6
|
+
|
7
|
+
* tork-engine(1): list most recently ran test files in `:idle` event. This
|
8
|
+
allows tork(1) to summarize a run after tests finish running, as follows:
|
9
|
+
|
10
|
+
tork: 10 tested, 10 passed, 0 failed
|
11
|
+
|
12
|
+
* tork-engine(1): add `list_failed_test_files` command that lists all test
|
13
|
+
files that have failed during their most recent run.
|
14
|
+
|
15
|
+
tork(1): add `l` key (bound to the `list_failed_test_files` command).
|
16
|
+
|
17
|
+
Thanks to Chris Scharf for contributing this feature in issue-60:
|
18
|
+
https://github.com/sunaku/tork/pull/60
|
19
|
+
|
20
|
+
### Patch:
|
21
|
+
|
22
|
+
* tork/config: auto-detect `$TORK_CONFIGS` values only once per session.
|
23
|
+
This makes Tork load configuration helpers faster on slow file-systems.
|
24
|
+
|
25
|
+
* Use block-form of Dir.glob() to react more quickly on slow file-systems.
|
26
|
+
This makes tork-driver(1)'s `run_all_test_files` command more responsive.
|
27
|
+
|
28
|
+
### Other:
|
29
|
+
|
30
|
+
* Align error/help message wording with manual pages.
|
31
|
+
|
1
32
|
## Version 19.9.0 (2014-07-17)
|
2
33
|
|
3
34
|
### Minor:
|
data/man/man1/tork-driver.1
CHANGED
data/man/man1/tork-driver.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-driver.1</span></div></div><div class="container-fluid"><h1 id="tork-driver-1-2014-
|
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-08-06-19-10-0"><a name="tork-driver-1-2014-08-06-19-10-0" href="#tork-driver-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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
|
data/man/man1/tork-engine.1
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
.TH TORK\-ENGINE 1 2014\-
|
1
|
+
.TH TORK\-ENGINE 1 2014\-08\-06 19.10.0
|
2
2
|
.SH NAME
|
3
3
|
.PP
|
4
4
|
tork\-engine \- wraps
|
@@ -49,6 +49,9 @@ Runs all test files that have passed during their most recent run.
|
|
49
49
|
\fB\fC["rerun_failed_test_files"]\fR
|
50
50
|
Runs all test files that have failed during their most recent run.
|
51
51
|
.TP
|
52
|
+
\fB\fC["list_failed_test_files"]\fR
|
53
|
+
Lists all test files that have failed during their most recent run.
|
54
|
+
.TP
|
52
55
|
\fB\fC["quit"]\fR
|
53
56
|
Stops all tests that are currently running and exits.
|
54
57
|
.SS Output
|
@@ -56,8 +59,10 @@ Stops all tests that are currently running and exits.
|
|
56
59
|
This program prints the following messages, which are single\-line JSON arrays,
|
57
60
|
to stdout.
|
58
61
|
.TP
|
59
|
-
\fB\fC["idle"]\fR
|
60
|
-
All tests have finished running and no tests
|
62
|
+
\fB\fC["idle",\fR \fIran\fItest\fPfiles\fP\fB\fC,\fR \fIpassed\fItest\fPfiles\fP\fB\fC,\fR \fIfailed\fItest\fPfiles\fP\fB\fC]\fR
|
63
|
+
All queued tests have finished running and no new tests have been queued.
|
64
|
+
In particular, \fIran\fItest\fPfiles\fP test files have run, \fIpassed\fItest\fPfiles\fP
|
65
|
+
test files have passed, and \fIfailed\fItest\fPfiles\fP test files have failed.
|
61
66
|
.TP
|
62
67
|
\fB\fC["pass_now_fail",\fR \fItest_file\fP\fB\fC,\fR \fImessage\fP\fB\fC]\fR
|
63
68
|
A previously passing \fItest_file\fP has now failed. See \fImessage\fP for details.
|
data/man/man1/tork-engine.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-engine.1</span></div></div><div class="container-fluid"><h1 id="tork-engine-1-2014-
|
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-08-06-19-10-0"><a name="tork-engine-1-2014-08-06-19-10-0" href="#tork-engine-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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
|
@@ -16,7 +16,9 @@ execution overhead, and then re-runs those stopped test files.</dd></dl><dl><dt>
|
|
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="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"
|
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>["list_failed_test_files"]</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,
|
20
|
+
to stdout.</p><dl><dt><code>["idle",</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
|
+
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>["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 this Tork process on startup.
|
21
23
|
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
24
|
</html>
|
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-2014-
|
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-08-06-19-10-0"><a name="tork-herald-1-2014-08-06-19-10-0" href="#tork-herald-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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
data/man/man1/tork-master.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-master.1</span></div></div><div class="container-fluid"><h1 id="tork-master-1-2014-
|
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-08-06-19-10-0"><a name="tork-master-1-2014-08-06-19-10-0" href="#tork-master-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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,
|
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-2014-
|
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-08-06-19-10-0"><a name="tork-notify-1-2014-08-06-19-10-0" href="#tork-notify-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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-runner.1
CHANGED
data/man/man1/tork-runner.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-runner.1</span></div></div><div class="container-fluid"><h1 id="tork-runner-1-2014-
|
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-08-06-19-10-0"><a name="tork-runner-1-2014-08-06-19-10-0" href="#tork-runner-1-2014-08-06-19-10-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-08-06</span> <span class="md2man-source">19.10.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
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>
|
data/man/man1/tork.1
CHANGED
data/man/man1/tork.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.1</span></div></div><div class="container-fluid"><h1 id="tork-1-2014-
|
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-08-06-19-10-0"><a name="tork-1-2014-08-06-19-10-0" href="#tork-1-2014-08-06-19-10-0" class="md2man-permalink" title="permalink"></a><span class="md2man-title">TORK</span> <span class="md2man-section">1</span> <span class="md2man-date">2014-08-06</span> <span class="md2man-source">19.10.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
|
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.10.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-
|
12
|
+
date: 2014-08-06 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: md2man
|
@@ -128,31 +128,33 @@ files:
|
|
128
128
|
- lib/tork/bridge.rb
|
129
129
|
- lib/tork/cliapp.rb
|
130
130
|
- lib/tork/config.rb
|
131
|
-
- lib/tork/config/bundler/
|
131
|
+
- lib/tork/config/bundler/detect.rb
|
132
132
|
- lib/tork/config/bundler/master.rb
|
133
133
|
- lib/tork/config/coverage/master.rb
|
134
134
|
- lib/tork/config/coverage/worker.rb
|
135
|
-
- lib/tork/config/cucumber/
|
135
|
+
- lib/tork/config/cucumber/detect.rb
|
136
136
|
- lib/tork/config/cucumber/driver.rb
|
137
137
|
- lib/tork/config/cucumber/worker.rb
|
138
|
-
- lib/tork/config/devise/
|
138
|
+
- lib/tork/config/devise/detect.rb
|
139
139
|
- lib/tork/config/devise/onfork.rb
|
140
140
|
- lib/tork/config/devise/worker.rb
|
141
141
|
- lib/tork/config/dotlog/onfork.rb
|
142
|
-
- lib/tork/config/factory_girl/
|
142
|
+
- lib/tork/config/factory_girl/detect.rb
|
143
143
|
- lib/tork/config/factory_girl/onfork.rb
|
144
144
|
- lib/tork/config/factory_girl/worker.rb
|
145
145
|
- lib/tork/config/logdir/onfork.rb
|
146
146
|
- lib/tork/config/parallel_tests/worker.rb
|
147
|
-
- lib/tork/config/rails/
|
147
|
+
- lib/tork/config/rails/detect.rb
|
148
148
|
- lib/tork/config/rails/driver.rb
|
149
149
|
- lib/tork/config/rails/master.rb
|
150
150
|
- lib/tork/config/rails/worker.rb
|
151
151
|
- lib/tork/config/spec/config.rb
|
152
|
+
- lib/tork/config/spec/detect.rb
|
152
153
|
- lib/tork/config/spec/driver.rb
|
153
154
|
- lib/tork/config/spec/master.rb
|
154
155
|
- lib/tork/config/spec/worker.rb
|
155
156
|
- lib/tork/config/test/config.rb
|
157
|
+
- lib/tork/config/test/detect.rb
|
156
158
|
- lib/tork/config/test/driver.rb
|
157
159
|
- lib/tork/config/test/master.rb
|
158
160
|
- lib/tork/config/test/worker.rb
|