Re: Re: JRuby on Rails

There are many test cases we can use to test JRuby, and we use several
of those frequently. However, a failing of individual unit tests in
many cases is that they don't always test interactions between
multiple pieces of code. Code piece A and code piece B may work
correctly in themselves, but in interaction there may be side effects
that don't work as prescribed.

The approach we are taking is primarily focused directly on getting
Rails working, and so we spend most of our effort trying to run the
core Rails scripts themselves. As failures come up, we are generally
able to dig down to the appropriate level and find the problem, or
else pull out a small sample script that illustrates the same failure.
This process means that once we no longer have failures, we will have
Rails running. It certainly doesn't mean we'll be 100% compatible with
RoR or Ruby, but it achieves a single major goal. It also provides a
somewhat narrower target...fixing everything necessary to get Rails
*running* is certainly a subset of getting every component in Rails
running exactly as specified.

For outside parties, exercising small scripts or individual test cases
would be very illustrative and probably easier to swallow. Without a
knowledge of JRuby's internal workings, the approach of running
larger-scale scripts and apps and fixing the problems that arise can
be difficult.

On 2/22/06, Ahmed Mohombe <amohombe@xxxxxxxxx> wrote:
> > Really it comes down to finding "small interpreter failings".  Rails really
> > stresses JRuby.  Pick a rails thing (I did *some* work toward getting 
> > webrick
> > running with an "empty app"), and run it.  When something fails, figure out
> > why by digging through the Ruby code until you can narrow the failure down 
> > to
> > a small case.  The vast majority of these turn out to be easy to fix, but
> > you'll spend hours trying to make a small example of it.
> Hmm, isn't there a better approach (and less painful) ? E.g. using ready made 
> test cases like those
> for Ruby itself or even RoR? - so that one doesn't "invent" new "small cases" 
> but is using the
> existing one, thus being much more productive?
>
> Or am I totally overseeing something?
>
> Thanks in advance,
>
> Ahmed.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Jruby-user mailing list
> Jruby-user@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/jruby-user
>


--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642