Nothing was ever done, the rollbacks currently occur per test-suite as always.
Regards Scott On 10/11/2012, at 9:12 PM, Jacques Le Roux wrote: > Sorry to resurrect this old post, but what is the status on this? > > Thanks > > Jacques > > From: "Scott Gray" <[email protected]> >> We've had this discussion before, here is last one I could find: >> http://markmail.org/message/ftvs45vnzlobo7hb >> >> The solution I would like to propose for the problem David described >> is for us to make more use of the test-group child element of test- >> suite and have tests within those groups rollback as a group, for all >> other test cases we'd roll them back as soon as they complete. Here's >> an example of what I'm talking about since that description probably >> did nothing for you: >> >> <test-suite> >> >> <test-case/> >> <!-- Rollback here --> >> <test-case/> >> <!-- Rollback here --> >> <test-case/> >> <!-- Rollback here --> >> >> <!-- No rollbacks inside the test group --> >> <test-group> >> <test-case/> >> <test-case/> >> </test-group> >> <!-- Rollback here --> >> >> </test-suite> >> >> A common problem I'm seeing is that we want to run multiple tests on >> the same piece of demo data but can't because the previous test has >> already altered it. An example might be where you want to try >> shipping a single order in various different splits but you can't do >> that at the moment without having a separate demo order for each test. >> >> Thoughts? >> >> Thanks >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com >> >> >>
