in reply to A Framework for automated DB testing

I think I might consider making use of CVS or SVN or something similar in a case like this. One could use tags to get to known states of both data and schema. Your known state is a moving target here as you develop, so tagging across the schema/data sets would allow you to achieve numerous known past states. Should not be too tough to script a series of archive/db events to get to a known state using the tags.

...the majority is always wrong, and always the last to know about it...

  • Comment on Re: A Framework for automated DB testing