Robert Feldt <feldt / ce.chalmers.se> writes:

> We've got some nice lexer and parser tests coming up in the
> RubyInRubyParser project. Rich Kilmer is currently working on them. If we
> can find a way to use them in Rubicon that would be nice, I guess. We
> would probably have to (runtime?) patch parse.y to get the data we need or
> maybe we can use ruth which returns the internal tree (but then we can't
> test the lexer stand-alone). Ideas?

These sound like useful unit tests.

With Rubicon, I'm interested in testing the finished product: that it,
does the stuff produced by the lexer, parser by the parser, and run by
the interpreter do what it should. What I'd like to do it to have a
look at them when it's done and integrate what I can. At the same
time, perhaps we should look at using Rubicon as a test for the
overall integrated RiR.


Dave