to run under Ruby and the Fit framework. I have 2 questions. First I
get red results on last 3 tests because the precision in the HTML
table is only up to 8 digits, but Ruby is calculating 15 digits.
And second, even after I adjust the HTML to match the results, they
till don't equal. I am thinking this is because of '==' vs. eql? on
floats.
Is there a way coerce a Ruby float to an aribitray precision via
truncate or round?
to run under Ruby and the Fit framework. I have 2 questions. First I
get red results on last 3 tests because the precision in the HTML
table is only up to 8 digits, but Ruby is calculating 15 digits.
And second, even after I adjust the HTML to match the results, they
till don't equal. I am thinking this is because of '==' vs. eql? on
floats.
Is there a way coerce a Ruby float to an aribitray precision via
truncate or round?
If I remember correctly, there once was rumor that Dave Thomas was working
on a FIT-like framework for Ruby ...
I wonder whatever happened to that project...
I think that is the one I d/l from the wiki. Not sure though.
I've written a little ruby replacement of FIT ... I'll probably post it if
we don't find that someone else has already done the work.
Haven't taken the next step and built it into a wiki like the FITnesse
project ...
There is a version of RubyFIT in CVS on RubyForge. I tried it out and
it ran the Simple example (eg.Division) right out of the box. Solves
the precision problem by using a type adapter. Looking forward to how
that code addresses the 5 digit precision issue in Java v. Ruby.
So take a look at that one. If yours is better/different somehow, go
ahead and post it.