Order of Tests

OK. I guess my logic would've been like this: testOne: variables.someValue = "[some value]" testTwo: if strcutKeyExists( variables , "someValue") - run the test else fail("required value wasn't made") Thanks for the help > No, each test starts with a clean slate.  Otherwise you would haveso > many dependencies in the later tests that you wouldn't know if they > really failed or if something that went wrong in an earrlier test was > the problem > > David Harris wrote: > > Hi, > > > > I am in the process of setting up some tests, and have a situation where I would like to use the results of one test in another test. > > > > EG: > > > > testOne checks I can create a new instance of ABCComponent in the database, and the "create" function returns the key for that instance > > > > testTwo attempts to delete the instance created in testOne > > > > Is it possible to control the order of the tests to this level? > > > > Thanks > > > > David > > > > > >