Excellent, Pit! Many new nuggets of Rubyness for me to chew on here,
many thanks for taking the time on this Holiday to reply.
The question is: what do you want to do with the current list of failures?
As I mentioned, I’m exploring Test::Unit to better understand what’s
going on under the surface. I don’t have a particular need other than
familarization and dexterity with Ruby.
However, it seems that one must be able to locate the instance of
Test::Unit::TestResult in order to invoke it’s #add_observer() method,
ja? Or perhaps there is a more direct way to Observe what is
happening? Again, I’m just curious at this point, but some context of
my project might help:
I wish to create a Ticket Box Office for my wife’s theater company. It
is a facinating little problem, involving a neat little Domain Model of
Venues, Performances, Seats, Reservations, and the like. I’m starting
my Ruby journey by implementing a core concept, the Venue. It will be
a simple CRUD use case/user story(ies), but will lead to such fun as
SeatMaps and whatnot. Once I feel like I have sufficent understanding
of the Standard API, I’ll move on to Rails and let the web fun begin!
Many thanks again for the code example…runs of to start chewing…