Comments on Rhino and other beasts: Doctest in Rhino

tschaub: Have you looked at org.mozilla.javascript...

2009-08-19T08:48:03.656-04:00

tschaub: Have you looked at org.mozilla.javascript.tests.DoctestsTest? This is a JUnit test that calls runDoctest. Does that do what you want?

Can doctest be run in another scope? I can't figu...

2009-08-18T23:15:31.878-04:00

Can doctest be run in another scope? I can't figure out how to get at runDoctest from the shell, but I think that provides what I would like to do (basically, run doctest without polluting global - and call it multiple times with the same scope). Thanks for any tips.

tschaub: You're right that true and "true" print t...

2009-06-17T21:45:46.369-04:00

tschaub: You're right that true and "true" print the same. I'll often write my doctests to print out the value and the type:

js> function f() { return true; }
js> var x = f();
js> x
true
js> typeof x
boolean

Beyond that, it would be generally useful to have a more descriptive output format for the shell; perhaps a special global function that, if defined, will be called to print the results of each expression on the command line (similar to the prompts variable now).

This is cool. Will future versions of rhino disti...

2009-06-17T18:39:02.773-04:00

This is cool. Will future versions of rhino distinguish between 'true' and true in console output (or ['foo'] and 'foo' etc.)? Seems like that would make these tests more useful.

Here's a link to JDoctest, based on your Rhino wor...

2009-02-04T20:44:00.000-05:00

Here's a link to JDoctest, based on your Rhino work. Thanks again!

I'm using this to implement a @doc.test tag for ja...

2009-02-04T19:15:00.000-05:00

I'm using this to implement a @doc.test tag for javadoc, and it's very nice -- thank you!

One minor issue: it's hard to write doc tests that are *supposed* to throw exceptions. I can't set the error reporter in the context, since Global.runDoctest overrides it. I *suspect* that ToolErrorReporter.reportException(RhinoException) should invoke we.getWrappedException().printStackTrace(err) instead of we.printStackTrace(err)? That gives me the actual Java exception involved -- and then Global.doctestOutputMatches would need to implement either doctest.ELLIPSIS or doctest.IGNORE_EXCEPTION_DETAIL to allow the body of the stack trace to be elided.