On Apr 19, 2005, at 6:07 PM, Adam Kennedy wrote:
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).
Yes, I think that this is what I'll do for the harness.
Your tests can write out to this document, and the harness c
David Wheeler wrote:
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 mor
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 e
* 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, but it'd be
good to allow users to define alternate outputs (tests may not always
run in a browser, eh?). Maybe
On Apr 12, 2005, at 2:07 PM, David Wheeler wrote:
I'm pleased to announce the second alpha release of TestSimple, the
port of Test::Builder, Test::Simple, and Test::More to JavaScript.
And you can download it from here:
http://www.justatheory.com/downloads/TestSimple-0.02.tar.gz
Cheers,
David
I'm pleased to announce the second alpha release of TestSimple, the
port of Test::Builder, Test::Simple, and Test::More to JavaScript. This
release has the following changes:
- Removed eqArray() and eqAssoc() functions from TestMore per
suggestion from Michael Schwern. The problem
