Running java -jar ../buildscripts/lib/custom_rhino.jar runner.js on the tagged version of 0.9.0 throws a lot of exceptions for me, not sure if this isn't the intention of the command line tool or maby my cygwin environment is buggered up, the first Exception i get looks like so:
Exception in thread "Thread-8" org.mozilla.javascript.EcmaError: TypeError: Cannot find function debug.
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3331)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3321)
at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3337)
at org.mozilla.javascript.ScriptRuntime.typeError1(ScriptRuntime.java:3349)
at org.mozilla.javascript.ScriptRuntime.notFunctionError(ScriptRuntime.java:3409)
at org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2043)
at org.mozilla.javascript.gen.c6._c10(Unknown Source)
at org.mozilla.javascript.gen.c6.call(Unknown Source)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:387)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2822)
at org.mozilla.javascript.gen.c6.call(Unknown Source)
at org.mozilla.javascript.Context.call(Context.java:547)
at org.mozilla.javascript.JavaAdapter.callMethod(JavaAdapter.java:492)
What i'd really like to do is unit test some of my tests; as far as i can tell there is no obvious way to pass only my set of tests via the command line, i was hopeing that ther'ed be something similar to the browser test case I.E.
$ java -jar ../buildscripts/lib/custom_rhino.jar runner.js testUrl=path/to/my/tests/module.js

testModule
I am also seeing this error and it seems to have something to do with ItemFileReadStore and ItemFileWriteStore. If I comment those two tests out of /dojo/tests/data.js, the entire Dojo directory passes the DOH Unit tests. But with those two items included in the tests, I get an endless loop of errors like the one posted above. Strangely, these tests pass just fine when run from the browser.
However, there is a way to do what you are asking above. The trick is, in addition to the command you tried, you need to include a testModule argument that gives the name of the package you are testing, like this:
it's a long neglected bug. I'll file something in trac.