Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

BUSTER_REPORTER environment variable is not honoured? #214

Closed
estebanm opened this issue Jul 4, 2012 · 2 comments
Closed

BUSTER_REPORTER environment variable is not honoured? #214

estebanm opened this issue Jul 4, 2012 · 2 comments
Assignees
Labels
Milestone

Comments

@estebanm
Copy link

estebanm commented Jul 4, 2012

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".

@cjohansen
Copy link
Member

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.

@ghost ghost assigned cjohansen Jul 5, 2012
@ghost ghost assigned dwittner Jan 13, 2014
@dwittner
Copy link
Member

Fixed by bcb644ff90.

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$ 

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants