You can see what the tests look like by loading the files in the tests/ directory into your Web browser. This is my first stab at what I hope becomes a complete port. I could use some feedback/ideas on a number of outstanding issues:
- I have no idea how to exit execution of tests other than by throwing an
skipRest()do not work.
- Skip and Todo tests currently don’t work because named blocks (e.g.,
todo(), instead. This is a rather different interface than that supported by Test::More, but it might work. Thoughts?
- Currently, one must call
Test._ending()to finish running tests. This is because there is no
_ending()are welcome. It might work to have the
onloadevent execute it, but then it will have to look for the proper context in which to append it (a
<pre>tag, at this point).
- Anyone have any idea how to get at the line number and file name in a
level()will have any part to play.
approach to have TestMore.js and TestSimple.js load TestBuilder.js.
I’d also like to use it to implement
loadOk()(equivalent to Test::More’s
More details are in the ToDo section of the TestBuilder docs.
Let me know what you think!
Looking for the comments? Try the old layout.