On Apr 16, 2005, at 3:00 PM, Adam Kennedy wrote:
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.
"machine county mode"? Just that, I think.
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.
Not really following all these comments. Can you provide more detail?
Consider the idea of creating a Document that doesn't actually exist in a window and is thus not seen. (I believe this is possible).
Your tests can write out to this document, and the harness can do counting of test results without spewing the entire test results to the screen.
The harness can then print the summary of the test results directly to the screen, in the same way we get either a "show all test results" or "show the summary of all the tests".
Once you are writing to an invisible document, why are you using a document? :) Just use an Array, or file-handle-like thing. Or perhaps an object that mocks/simulates a document, so that if you want to run just a single test, it will print out to the document, but in harness mode it's writing to an internal fake document.
Help?
Adam K
