Could be, like I said async services can't be rolled back at the moment. We're usually just left with a few CommunicationEvent records from order confirmation emails and there's also a TestingType record created by the service engine tests which causes an entity engine test to fail on subsequent runs. I'll fix it eventually but I've been waiting for the execution branch to come through so I don't have to possibly solve the problem twice.
Regards Scott On 22/01/2010, at 8:03 AM, Chris Snow wrote: > I seems that data created in one test case (e.g. a created workEffort) is > still in the db when I run the next test case. > > Scott Gray wrote: >> There was a reason I didn't do this, I just can't remember what it was. >> Thinking about it freshly, the reason was most likely that asynchronous >> service calls can't be rolled back currently (they're executed by the >> JobManager with a regular delegator) and rolling back the sequence ids would >> cause problems unless we can roll back absolutely everything. >> >> Regards >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com >> >> On 21/01/2010, at 10:30 AM, Chris Snow wrote: >> >> >>> It appears that test data gets rolled back after a test, EXCEPT for >>> sequence id's. >>> >>> I would expect all data generated during a test to get rolled back. >>> >>> Any comments? >>> >>> Many thanks, >>> >>> Chris >>> >> >> >
smime.p7s
Description: S/MIME cryptographic signature
