TidyTest.jl

An AbstractTestSet implementation and a helper macro for test execution with auto discovery and a neater test summary.

Within Julia, execute

using Pkg; Pkg.add("TidyTest")

For the simplest use case, write the following lines in your runtests.jl file:

using TidyTest

@run_tests

Add TidyTest.jl to the dependencies of your test:

julia> using Pkg; pkg"activate test; add TidyTest"

And then execute your tests:

julia --project -e "using Pkg; Pkg.test()"

For example:

The @run_tests macro automatically discovers all Julia source files in the directory of runtests.jl, and includes all of them. The entire block of includes is wrapped in a single toplevel @testset using the custom test set type SpinnerTestSet. Test progress is reported using ProgressMeter.jl, continuously updating the status as tests are completed. If some tests fail (or throw an error), the issues are reported as they happen, and a detailed test summary is printed upon completion, using the default test reporting.

The macro facilitates running tests selectively. Every command line argument is treated as a pattern that narrows the set of included test files. Specifically, only test files with a name containing any of the arguments as a substring are included. The search uses smart case matching: if any of the patterns contains at least one capital letter, then matching is case-sensitive, otherwise it is case-insensitive. To pass command line arguments to Pkg.test(), the test_args keyword argument must be used:

$ alias jlt='julia --project -e "using Pkg; Pkg.test(test_args=ARGS)"'
$ jlt some tests
# ...runs test files which have "some" or "tests" occurring in their names

Alternatively, one can filter tests by passing a filters keyword argument to the @run_tests macro, with a list of strings:

@run_tests filters=["some", "tests"]

To start using TidyTest.jl in an existing package, perform the following steps:

1. add TidyTest.jl to the dependencies of your test (as above);

2. rename your existing "runtests.jl" file (e.g., "MyModule.jl", but any name other than "runtests.jl" works);

3. add a new "runtests.jl" file with "using TidyTest; @run_tests" as its contents (as above).

And you are all set. Optionally, if you want to use the test filtering functionality, break up your unit tests into multiple files, placing a single test set in every file.

Here are some more examples, run in the sample directory of this repository.

When there are some tests that fail and/or throw an error, the issues are reported immediately, the progress line is printed in red, and a detailed summary is printed upon completion:

When there are passing tests only, no details are shown. The color of the progress line stays green:

Filtering is case-sensitive when the pattern contains uppercase characters. Also, when there are broken tests, the color of the progress line turns yellow, but still no details are printed:

Detailed reporting can be forced with the verbose=true keyword argument even for passing tests:

@run_tests [name] [dir="."] [filters=ARGS] [rest...]

Discover and include test (Julia) files from the directory of the caller, and wrap them in a SpinnerTestSet for reporting. The name of the testset is automatically derived from the package name, if the macro is called from the runtests.jl file.

Optional arguments:

• name: explicitly name the testset;

• dir=".": discover tests in the provided directory (defaults to the directory of the source file that contains the macro call);

• filters=[...]: filter discovered source files - include only those which contain any of the filter strings as a substring (defaults to the command line arguments);

• all other keyword arguments are passed directly to SpinnerTestSet.

Filtering uses smart case matching: if any of the patterns contains at least one capital letter, then matching is case-sensitive, otherwise its case-insensitive.

SpinnerTestSet(desc::String; [width::Integer, verbose::Bool, rest...])

An implementation of Test.AbstractTestSet, that reports testing progress using ProgressMeter.ProgressUnknown, continuously updating the status as tests are completed.

Arguments:

• desc: the name of the testset;

• width: the display width of the progress line (defaults to the width of the terminal);

• verbose: whether to print a detailed summary even when none of the tests fail or throw an error (defaults to false);

• all other keyword arguments are passed directly to Test.DefaultTestSet.

• TestSetExtensions.jl