Tork - test with fork
___ /___________ /__
_ _/ __ \ / //
/ // // / / / ,
Tork runs your tests as they change, in parallel:
Absorbs test execution overhead into a master process.
Forks to inherit overhead and run test files in parallel.
Avoids running unchanged tests inside changed test files.
.tork.rbconfiguration file has been replaced by the
directory, which contains specially-named Ruby scripts. Refer to
TORK_CONFIGSenvironment variable in tork(1) for more information.
Tork::Configobject has been replaced by various data
Tork::namespace. See the “FILES” sections in the manual
tork programs for information on the data structures that replaced
Tork::Config.test_event_hookshas been removed. Instead, you must
monitor the STDOUT of tork-master(1) or tork-engine(1) either
or indirectly, via tork-remote(1), and react to their status
See the tork-notify(1) program for an example of how to implement
tork(1): ‘t’ now runs a specified test, whereas ‘a’ runs all tests.
run_test_filecommand now takes line numbers
variable-length list of arguments (varargs) rather than as an array.
run_test_filecommand now runs an entire test
when zero is given as one of the line numbers to be run.
loadcommand is no longer accepted. Instead,
must specify load paths and overhead files in the
TORK_CONFIGSenv-var is now a colon delimited list of
tork/clientlibrary has been removed. The threaded IO and
wrappers that it provided have been replaced by the powerful
tork(1): allow user to specify arguments after command key
tork(1): add ‘k’ to stop all currently running tests with SIGKILL
add tork-remote(1) to remotely control any tork program. This
made possible by the awesome power of IO.select() and UNIX domain
add tork-notify(1) as example of using tork-remote(1) and
["run_test_files"]command to run multiple
tork-engine(1): emit edge-triggered
events to notify you about changes in a test file’s pass/fail
typing Control-D now breaks tork programs out of
- tork-master(1): stop workers with SIGKILL when quitting
tork(1): document parameters for
README: add tip about rlwrap for better interactive
README: simplify watch command using pgrep & xargs
README: use standard bundle exec; no