Makes sense. There is a nextTransaction() method in the AbstractIntegTest class, you could see how that is implemented and see if it can be adapted?
Or, another idea is that the framework could run each FixtureScript automatically in a separate transaction; that would be a better simulation of a sequence of user interactions? Thoughts? Dan On 28 May 2015 12:39, "GESCONSULTOR - Óscar Bou" <[email protected]> wrote: > Hi all. > > When using FixtureScripts, there can be many actions that, on the real > world, are execute in different time contexts. > > For example, a user creates an Account on the webapp and after that > executes different actions. > > That’s relevant if using the queryResultsCache service (or the new planned > “@Action” annotation extension) because the results previously created > (i.e., the Account) might be available on the cache. > > So perhaps some mechanism like the nextTransation() method might be also > introduced on FixtureScripts. > > What do you think? > > Regards, > > Oscar > > > > >
