Open GCheung55 opened 9 years ago
Why do you want to use buster-ci
for node testing instead of buster-test
? The intention of buster-ci
is to provide a comfortable way to run browser tests, without the need to start buster-server
, capture the browsers and run the tests.
This feature would be beneficial because it's able to output an XML file without the uncaughtExceptions that is logged to stdout, unlike buster-test.
buster-ci
should behave just the same as buster-test --reporter xml 1> output.xml
.
But it isn't the same because the warning log shows up, as described in #439, in the output.xml.
buster-ci
doesn't show the warning log in the output.xml.
But the warnings only show up for browser tests, right? I don't see them for node tests.
Did you try the code from https://github.com/busterjs/buster/issues/439#issuecomment-70771996 ?
buster-ci
only runs browser tests and it should be able to run node tests.