Hi Scott,
It's not a problem with the test framework, it is with my custom demo
data. In my demo data, I was creating workEfforts with id's of 10020
and 10030.
During testing I was creating more workEfforts. At one stage, the tests
were failing because the new workEfforts were getting already used
workEffortId's.
I need to change my test data to use lower workEffortId's or change the
sequence to start at a higher value. Which would be the preferred ofbiz
approach?
Many thanks,
Chris
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
