Test options¶
- Version:
- See buster-test
The command buster test accepts the following options:
-
-h
,
--help
¶
Show usage help. See also
--help reporters
.
-
-l
,
--log-level
¶
Set logging level. One of error, warn, log, info, debug.
-
-v
,
--verbose
¶
Increase verbosity level. Include one (log level
info
) or two times (e.g.-vv
, for log leveldebug
).
-
-c
,
--config
¶
Test configuration file.
-
-g
,
--config-group
¶
Test configuration group(s) to load.
-
-t
,
--tests
¶
Test files (within active configuration) to run.
-
-e
,
--environment
¶
Test configuration environment to load.
-
-r
,
--reporter
¶
Test output reporter Default is dots.
-
-C
,
--color
¶
Output color scheme. One of
dim
,bright
,none
. Default isbright
.
-
-s
,
--server
¶
Hostname and port to a running buster-server instance (for browser tests). Default is
http://localhost:1111
.
-
-R
,
--reset
¶
Don’t use cached resources on the server.
-
-W
,
--warnings
¶
Warnings to print. One of
fatal
,error
,warning
,all
,none
. Default isall
.
-
-F
,
--fail-on
¶
Fail on warnings at this level. One of
fatal
,error
,warning
. Default isfatal
.
-
-L
,
--log-all
¶
Log all messages, including for passed tests.
-
-o
,
--release-console
¶
By default, Buster captures log messages from
console.log()
and friends. It does so by replacing the globalconsole
object with thebuster.console
object. This option skips this hijacking.
-
-p
,
--static-paths
¶
Serve files over a static URL on the server. Reusing paths across test runs makes it possible to use breakpoints, but increases the risk of stale resources due to due to the browser caching too eagerly.