* Decide where to send test output, and where to allow other output to be sent. Test::Builder clones STDERR and STDOUT for this purpose. We'll probably have to do it by overriding C<document.write()>, but it'd be good to allow users to define alternate outputs (tests may not always run in a browser, eh?). Maybe we can use an output object? Currently, a browser and its DOM are expected to be present. I could really use some advice from real JavaScript gurus on this one.
It's going to totally depend on what you want to wrap around it...
Do you want the human interacty mode? Or the machine county mode.
Forget the document object for a moment, you are more accurately in the ever present window when you are running.
I just finished Class::Adapter, so I'm currently imagining some sort of basic IO Adapter...
TestOutputArray just appends to an internal array, TestOutputDocument appends to window.document...
Or you could just create an anonymous document object, and use that for the internal case.
Adam K
