From: Brian Candler <B.Candler@...>
Date: 2003-05-15T17:25:45+09:00
Subject: Test::Unit sequencing

A question for more experienced Test::Unit users.

I want to do a fairly complex sequence of tests which carries state between
them: e.g. create a blank database, call some methods which should create
some entries, then test they are there, call some other methods which should
find and update those entries, test they have been changed, and so on.

I can use 'setup' to create the empty environment, but how do I make sure
all the other tests are performed in the right sequence? Should I just write
this all as one big test method?

Cheers,

Brian.