imhotap

This is a meta-test-framework. Point it at a set of test files and see the
output summarized for each file!

By default, imhotap will find files matching the glob test/*/test.js, and
will run each file individually. Each file that exits with a non-zero code will
be considered a test failure. The output is presented in TAP, but you can also
use whatever reporter you'd like.

No assumptions are made about what underlying test framework is used in each of
the files. If your tests produce TAP in either stdout or stderr, the output of
the first of those two streams that looks like TAP data will be treated as a
subtest. If neither stream looks like TAP data, both streams will be displayed
inside a YAML block.

Some test frameworks that should work well with imhotap are:

* pitesti
* tape
* node-tap
* Any other TAP producer

Usage

``
$ imhotap --help
Options:
--version Show version number [boolean]
--help Show help [boolean]
-f, --files glob pattern for while files to run
[array] [default: "test/*/test.js"]
-c, --concurrency how many test files to run in parallel (0 == Infinity)
[number] [default: 23]
-r, --reporter which tap reporter to use, or just tap
[string] [default: "tap"]
-q, --quieter whether or not to include subtests on success
[boolean] [default: false]
-R, --runner a script runner for running test files (e.g. tsnode, etc.)
[string]
-e, --test-env set an environment variable to the test file and runner
[array]
-s, --stream stream to expect TAP output from test files
[choices: "stdout", "stderr"] [default: "stdout"]
`

Without any additional options, imhotap will run with all the defaults.

$3

The -f/--files options can be used to specify which files are run, using a
glob (i.e. minimatch/fnmatch) pattern. For example, to match any files in your
test directory, and subdirectories, ending in .spec.js, you might use the
option -f test/*/.spec.js.

If matching files end in .js, they will be executed with node, otherwise (if
-R/--runner is not set) the matching files must be executable.

$3

It's expected that your test files can be run as separate process at the same
time. If that's not the case, or there's too much load on your computer, you can
adjust the the the number of simultaneous processes imhotap will spawn. For
example, -c 1 will tell imhotap to run only 1 file at a time. The default
is 1 less than the available CPU cores on your computer.

$3

While the default is to just output TAP, you can format it using any of the
various reporter tools that convert TAP into more pleasant output using stdin
and stdout. Many can be found
here.

To specify a reporter, use the -r/--reporter option. If a named reporter can't
be found on the $PATH, imhotap will attempt to run it using npx.

$3

You may want to use a different runner than node for executing your files. If
-R/--runner is set to some script runner name, that runner will be used to
execute your test files.

For example, if your test files are written in TypeScript, you may want to use
tsnode to execute your files. In that case, you can pass -R tsnode to
imhotap.

$3

It can be useful to set environment variables that apply to test files, but
not to imhotap itself. You can use the -e/--test-env option to set one or
more environment variables.

For example, to set FOO=bar and BAZ=bux in the test environment, you can
pass -e FOO=bar BAZ=bux to imhotap.

$3

By default, imhotap will show subtest data from either stdout or stderr as
described above, or just output the streams in a YAML block if no TAP output is
found. In either case, if you'd like more terse output, you can use the
-q/--quieter option to hide all but the top-level TAP produced by imhotap.

$3

You can also provide config in package.json using the "imhotap" property.
For example, to set the file pattern, to test-*.js, your package.json can look
like this:

`js
{
"name": "myapp",
"scripts": {
"test": "imhotap"
},
// ...
"dependencies": {
// ...
},
"devDependencies": {
"imhotap": "*"
},
"imhotap": {
"files": "test-*.js"
}
}
``

License

MIT License. See LICENSE.txt.