Brian Marick wrote:
> 
> So, questions:
> 1) Who's got code?
> 2) Who's willing to write code?
> 3) Who's got success stories to share?
> 4) Who's got ideas about spreading the word to testers?
> 5) What are those ideas?

First let's get things out in the open: I'm a rocket
scientist that does some coding in Fortran. :)
[a reference to the conclusion slide in Nathaniel's
testing talk, see http://www.rubyconf.org]

Now, on to the testing part: I'm on a team which has to
deal with legacy Fortran code and I've written a Fortran
/developer|mobility|unit/ testing application in Ruby
(which has not been released yet).

Does that count toward having/writing code?  We haven't
starting using it in practice yet, so no success/failure
stories to share yet...

Currently the tests are written in pseudo Fortran and Ruby
expands the tests into legal Fortran, compiles everything,
and runs the tests.  I am doing things this way for two
reasons: (1) acceptance by Fortran people (i.e., they do
not have to learn Ruby to be able to write tests), (2) I
have been too lazy (or is it stupid? ;) thus far to figure
out how to wrap Fortran code with Ruby.

--
bil <http://abweb.larc.nasa.gov/~kleb/>
(currently blocked due to security paranoia)