- RUN PROJECT TESTS
- PRELOAD MODULES
- PER-TEST TIMING DATA
- PERSISTENT RUNNER
- MAKING YOUR PROJECT ALWAYS USE YATH
- PROJECT-SPECIFIC YATH CONFIG
- PROJECT-SPECIFIC YATH CONFIG USER OVERRIDES
- HARNESS DIRECTIVES INSIDE TESTS
- MODULE DOCS
App::Yath - Yet Another Test Harness (Test2-Harness) Command Line Interface (CLI)
PLEASE NOTE: Test2::Harness is still experimental, it can all change at any time. Documentation and tests have not been written yet!
The canonical source of up-to-date command options are the help output when using
$ yath help and
$ yath help COMMAND.
This document is mainly an overview of
yath usage and common recipes.
To use Test2::Harness, you use the
yath command. Yath will find the tests (or use the ones you specify) and run them. As it runs, it will output diagnostic information such as failures. At the end, yath will print a summary of the test run.
yath can be thought of as a more powerful alternative to
These are common recipes for using
Simply running yath with no arguments means "Run all tests for the current project". Yath will look for tests in
./test.pl and run any which are found.
Normally this implies the
test command but will instead imply the
run command if a persistent test runner is detected.
Yath has the ability to preload modules. Yath normally forks to start new tests, so preloading can reduce the time spent loading modules over and over in each test.
Note that some tests may depend on certain modules not being loaded. In these cases you can add the
# HARNESS-NO-PRELOAD directive to the top of the test files that cannot use preload.
Any module can be preloaded:
$ yath -PMoose
You can preload as many modules as you want:
$ yath -PList::Util -PScalar::Util
If your preload is a subclass of Test2::Harness::Preload then more complex preload behavior is possible. See those docs for more info.
You can turn on logging with a flag. The filename of the log will be printed at the end.
$ yath -L ... Wrote log file: test-logs/2017-09-12~22:44:34~1505281474~25709.jsonl
The event log can be quite large. It can be compressed with bzip2.
$ yath -B ... Wrote log file: test-logs/2017-09-12~22:44:34~1505281474~25709.jsonl.bz2
gzip compression is also supported.
$ yath -G ... Wrote log file: test-logs/2017-09-12~22:44:34~1505281474~25709.jsonl.gz
-G both imply
You can replay a test run from a log file:
$ yath test-logs/2017-09-12~22:44:34~1505281474~25709.jsonl.bz2
This will be significantly faster than the initial run as no tests are actually being executed. All events are simply read from the log, and processed by the harness.
You can change display options and limit rendering/processing to specific test jobs from the run:
$ yath test-logs/2017-09-12~22:44:34~1505281474~25709.jsonl.bz2 -v 5 10
Note: This is done using the
$ yath replay ... command. The
replay command is implied if the first argument is a log file.
-T option will cause each test file to report how long it took to run.
$ yath -T ( PASSED ) job 1 t/App/Yath.t ( TIME ) job 1 0.06942s on wallclock (0.07 usr 0.01 sys + 0.00 cusr 0.00 csys = 0.08 CPU)
yath supports starting a yath session that waits for tests to run. This is very useful when combined with preload.
This starts the server. Many options available to the 'test' command will work here but not all. See
$ yath help start for more info.
$ yath start
This will run tests using the persistent runner. By default, it will search for tests just like the 'test' command. Many options available to the
test command will work for this as well. See
$ yath help run for more details.
$ yath run
Stopping a persistent runner is easy.
$ yath stop
which command will tell you which persistent runner will be used. Yath searches for the persistent runner in the current directory, then searches in parent directories until it either hits the root directory, or finds the persistent runner tracking file.
$ yath which
watch command will tail the runner's log files.
$ yath watch
You can use preloads with the
yath start command. In this case, yath will track all the modules pulled in during preload. If any of them change, the server will reload itself to bring in the changes. Further, modified modules will be blacklisted so that they are not preloaded on subsequent reloads. This behavior is useful if you are actively working on a module that is normally preloaded.
$ yath init
The above command will create
test.pl is automatically run by most build utils, in which case only the exit value matters. The generated
test.pl will run
yath and execute all tests in the
./t2 directories. Tests in
./t will ALSO be run by prove but tests in
./t2 will only be run by yath.
You can write a
.yath.rc file. The file format is very simple. Create a
[COMMAND] section to start the configuration for a command and then provide any options normally allowed by it. When
yath is run inside your project, it will use the config specified in the rc file, unless overridden by command line options.
Comments start with a semi-colon.
[test] -B ;Always write a bzip2-compressed log [start] -PMoose ;Always preload Moose with a persistent runner
This file is normally committed into the project's repo.
You can add a
.yath.user.rc file. Format is the same as the regular
.yath.rc file. This file will be read in addition to the regular config file. Directives in this file will come AFTER the directives in the primary config so it may be used to override config.
This file should not normally be committed to the project repo.
yath will recognise a number of directive comments placed near the top of test files. These directives should be placed after the
#! line but before any real code.
Real code is defined as any line that does not start with use, require, BEGIN, package, or #
- good example 1
#!/usr/bin/perl # HARNESS-NO-FORK ...
- good example 2
#!/usr/bin/perl use strict; use warnings; # HARNESS-NO-FORK ...
- bad example 1
#!/usr/bin/perl # blah # HARNESS-NO-FORK ...
- bad example 2
#!/usr/bin/perl print "hi\n"; # HARNESS-NO-FORK ...
#!/usr/bin/perl # HARNESS-NO-PRELOAD
Use this if your test will fail when modules are preloaded. This will tell yath to start a new perl process to run the script instead of forking with preloaded modules.
Currently this implies HARNESS-NO-FORK, but that may not always be the case.
#!/usr/bin/perl # HARNESS-NO-FORK
Use this if your test file cannot run in a forked process, but instead must be run directly with a new perl process.
This implies HARNESS-NO-PRELOAD.
yath will usually kill a test if no events occur within a timeout (default 60 seconds). You can add this directive to tests that are expected to trip the timeout, but should be allowed to continue.
NOTE: you usually are doing the wrong thing if you need to set this. See:
yath can be told to alter the default event timeout from 60 seconds to another value. This is the recommended alternative to HARNESS-NO-TIMEOUT
yath can be told to alter the default POSTEXIT timeout from 15 seconds to another value.
Sometimes a test will fork producing output in the child while the parent is allowed to exit. In these cases we cannot rely on the original process exit to tell us when a test is complete. In cases where we have an exit, and partial output (assertions with no final plan, or a plan that has not been completed) we wait for a timeout period to see if any additional events come into
This lets you tell
yath that the test file is long-running. This is primarily used when concurrency is turned on in order to run longer tests earlier, and concurrently with shorter ones. There is also a
yath option to skip all long category tests.
This category is set automatically if HARNESS-NO-TIMEOUT is set.
This lets you tell
yath that the test is medium-length.
This category is set automatically if HARNESS-NO-FORK or HARNESS-NO-PRELOAD are set.
This lets you tell
yath that the test cannot be run concurrently with other tests. Yath will hold off and run these tests one at a time after all other tests.
This lets you tell
yath that the test cannot be run concurrently with other tests of this class. This is helpful when you have multiple tests which would otherwise have to be run sequentially at the end of the run.
Yath prioritizes running these tests above HARNESS-CATEGORY-LONG.
This is the default category.
This lets you tell
yath that no other test of type XXX can be run at the same time as this one. You are able to set multiple conflict types and
yath will honor them.
XXX can be replaced with any type of your choosing.
NOTE: This directive does not alter the category of your test. You are free to mark the test with LONG or MEDIUM in addition to this marker.
- Example with multiple lines.
#!/usr/bin/perl # DASH and space are split the same way. # HARNESS-CONFLICTS-DAEMON # HARNESS-CONFLICTS MYSQL ...
- Or on a single line.
#!/usr/bin/perl # HARNESS-CONFLICTS DAEMON MYSQL ...
This section documents the App::Yath module itself.
This is the entire
yath script, comments removed.
#!/usr/bin/env perl use App::Yath(\@ARGV, \$App::Yath::RUN); exit($App::Yath::RUN->());
- $class->import(\@argv, \$runref)
This will find, load, and process the command as found via
@argvprocessing. It will set
$runrefto a coderef that should be executed at runtime (IE not in the
BEGINblock implied by
Please note that statements after the import may never be reached. A source filter may be used to rewrite the rest of the file to be the source of a running test.
Print a message to STDOUT.
- $class->run_command($cmd_class, $cmd_name, \@argv)
Run a command identified by
- $cmd_name = $class->parse_argv(\@argv)
Determine what command should be used based on
\@argvmay be modified depending on what it contains.
- $cmd_class = $class->load_command($cmd_name)
Load a command by name, returns the class of the command.
The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/.
Copyright 2017 Chad Granum <email@example.com>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.