Florin Wach wrote:
...the restriction of having no db-changes possible with Test-Classes makes these one pretty much useless in Workflow's implementation
No no no, that's exactly what makes them so useful: Having a unit test that does not rely on what's stored in the DB, but is instead consistent and repeatable across all environments. But it's a bit more long winded to implement than simple application logic unit tests because you need a clean DB abstraction layer (which in itself is a good thing!).