For (a), I'm assuming you mean --output instead of --options. I actually had this on my TODO list to change to --format.

I'll take a look at the others as well. I had planned on adding code coverage support, I've just not had time to get to it yet.

(a) and (d) are complete and checked in.

I'm holding off on (b) for now pending some other changes. For the time being, you can redirect output using > output.txt

(c) will be included in a future edition.

I just checked out the latest build and see the --format option. Positive improvement.

The only quibble over redirecting output to a file is that it prevents the test author from having debugging output, which is a common usage. Yeah, looking forward to (b) being implemented. BTW it appears the code is using stderr.write and sys.print in different places and I don't know if that's on purpose or accidental.

It appears that the results get truncated.

I have a test suite(s) of a couple hundred tests run this way: yuitest --format junitxml test.js test_cache.js

I've arranged it so all of my tracing output goes to a separate file leaving the console for the test results (see previous comment for preferred behavior). The XML of the results doesn't fully print, instead it stops in mid-tag and my shell prompt gets printed. Hence the sys.print in YUITest.Node.CLI.Format must not be printing everything it gets.

As a quick hack idea I changed that to console.log and it had essentially the same behavior.

Another idea I had was this:

if (!process.stdout.write(format(results) + "n")) {
while (!process.stdout.write(" ")) { }
}

But it just got into a really long pause obviously due to the obvious infinite loop. It tells me that what's going on is stdout.write is returning false and according to the node.js documentation this means the output hasn't been fully flushed. Somehow what's needed is to pause and allow the output to drain...?

Spent awhile working on debugging this...

There's a note in the nodejs@googlegroups.com list about output being cut off if there's a process.exit(1) (the thread title is "redirecting output & exiting the process")

I found that hacking the handler in YUITest.Node.CLI.XUnit to call process.stdout.flush() several times, then all the output would go out.

I found that among the output not occurring is a COMPLETE_EVENT handler like this where it's using openSync, writeSync, closeSync to write the output. Somehow this handler never got called. Perhaps because of the handler in cli.js - which I've commented out. The test suite has failed tests, and that handler process.exit(1)'s if there are failures. Clearly doing exit(1) is useful but it needs to be coordinated with ensuring all the output occurs.

YUITest.TestRunner.subscribe(
YUITest.TestRunner.COMPLETE_EVENT,
function(event) {
log("test_cache " + event.type);
if (event.results) {
var res = YUITest.TestFormat.JUnitXML(event.results);
log('RESULTS: results-test_cache.xml');
trace.writeLogFile("results-test_cache.xml", res);
}
}
);