RE: saving state between fixtures

Hi Ward,

> > We could emulate that by giving Fixture a static hashtable to hold
> > test-specific state.
> 
> Fixture already holds such a hash, called summary, which it is careful 
> to pass to child fixtures, but not to new top level fixtures as created 
> by, for example, eg.AllFiles. This seems to be exactly the right 
> lifetime for cross-table state.

I confess: the summary hash was what inspired me. ;-)
 
> As an added feature, all such objects are reported in the fit.Summary, 
> if present.

Would that be desirable for the kind of state data that inspired the
original question?

Charlie Poole
[email protected]
www.pooleconsulting.com
www.charliepoole.org