[FLOW3-general] Phpunit: Mocking persistence/ aspects

[Martin Eisengardt]

> I think you should use @scope session for that. Example:
> Let's say I want to make a Blog Post "Transactional", i.e. want to
> update it during multiple requests, but update the changes in the
> database atomically.
I have use cases where multiple users are editing entities over multiple 
requests.
Some workflows where objects are sent to several users to do their edit 
action and
after that someone decides to commit or rollback those changes. Maybe the 
next thing
I will do is a workflow engine that is able to fetch user input; the 
workflow itself may not
know which user is asked for input and it may not be able to access the 
users session
if it performs the workflow in background (=cron job).
But having a session storage is interesting. Hmmm. I keep thinking of an 
abstraction level
of the storage.

> To me, this sounds more like Functional Tests, what you mean. Robert has
> just spent the last days to implement that; it has landed in trunk
> yesterday, and I think can be soon used.
Yep, the unit tests are finished for know :) I will have a look in the 
trunk. But
there are some changes I need to make first to be compatible ;-)