You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
It seems the BUSTER_REPORTER environment variable is not honoured when running tests with Buster (be that "buster test" or "buster-test"), but it does work when running "node path/to/test.js".
The text was updated successfully, but these errors were encountered:
This will be sorted out before the next beta/RC (http://busterjs.org/roadmap.html). In the meantime, BUSTER_TEST_OPT='-r xml' should serve the same purpose.
busterjs@ubuntu:~/example$ BUSTER_REPORTER=tap buster-test
ok 1 My example tests test refute
ok 2 My example tests test asynchronous
ok 3 My example tests test assert
1..3
busterjs@ubuntu:~/example$
If you use both, BUSTER_REPORTER=tap and -r specification, the reporter given by BUSTER_REPORTER will be used:
busterjs@ubuntu:~/example$ BUSTER_REPORTER=tap buster-test -r specification
ok 1 My example tests test refute
ok 2 My example tests test asynchronous
ok 3 My example tests test assert
1..3
busterjs@ubuntu:~/example$
It seems the BUSTER_REPORTER environment variable is not honoured when running tests with Buster (be that "buster test" or "buster-test"), but it does work when running "node path/to/test.js".
The text was updated successfully, but these errors were encountered: