package tezt
Test framework for unit tests, integration tests, and regression tests
Install
Dune Dependency
Authors
Maintainers
Sources
tezt-4.2.0.tar.bz2
md5=7878acd788ae59f1a07d0392644f0fff
sha512=b9e8ce2576b0bc65870409380edf17b88656a985ceb9a438a84f479b51d6b30740acf7b035eccf7d122bf5227611bf15e888e607dcdbb1576b4383f12314dd49
doc/tezt.core/Tezt_core/Cli/Logs/index.html
Module Cli.Logs
Source
Command-line arguments that control logging.
--color
, --no-color
--log-timestamp
, --no-log-timestamp
--log-prefix
, --no-log-prefix
Log levels for standard output.
The list below is sorted from the most quiet level to the most verbose level.
- Absolutely no log has log level
Quiet
. In other words, setting log levelQuiet
inhibits all logs.
Error
logs are about errors which imply that the current test failed. This includes messages given toTest.fail
and uncaught exceptions.
Warn
logs are about errors that do not cause the current test to fail. This includes failure to clean up temporary files, for instance.
Report
logs are informational messages that report the result of the current test. They tell the user whether the test was successful or not. They may also include information about how to re-run the test.
Info
logs are informational messages that summarize what the test is doing. They tell the user that a particular milestone was reached. In tests, it is a good idea to logInfo
messages at significant checkpoints.
Debug
logs give more details about exactly what is happening. They include external process outputs, exit codes, and signals which are sent.
Additionally, some flags such as --commands
and --list
cause some information to be printed unconditionally, even with --quiet
. Such kind of output is not considered to be log messages.
--log-file
--log-buffer-size
--log-worker-id
--commands
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>