- Defined options are:
- Determines whether or not tests are loaded. When
everything between begin_tests/1
is simply ignored. When
always, tests are always loaded.
Finally, when using the default value
normal, tests are
loaded if the code is not compiled with optimisation turned on.
- Specifies when tests are run. Using
manual, tests can only
be run using run_tests/0
make, tests will be run for reloaded files, but not
for files loaded the first time. Using
will run all test-suites, not only those that belong to files that are
- Currently one of
tty (default if there is a console) or
tty uses terminal control to overwrite
successful tests, allowing the user to see the currently running tests
and output from failed tests. This is the default of the output is a
log prints a full log of the executed tests and their
result and is intended for non-interactive usage.
always, emit all output as it is produced, if
suppress all output and if
on_failure, emit the output if
the test fails.
- Show individual blocked tests during the report.
- Defines the default for the
occurs_check flag during
false), cleanup report at the
Used to improve cooperation with memory debuggers such as dmalloc.
- Number of jobs to use for concurrent testing. Default is one, implying
- Set timeout for each individual test. This acts as a default that may be
overuled at the level of units or individual tests. A timeout of 0 or
negative is handled as inifinite.
.plt test-files that belong to the currently loaded
- Print all currently running tests to the terminal. It can be used to
find running thread in multi-threaded test operation or find the
currently running test if a test appears to be blocking.
- Print report on the executed tests. What defines the type of
report. Currently this only supports
details on how the fixme-flagged tests proceeded.