but from what I've read this will induce a significant performance penalty. I don't even want to know where you read that. I'll refer you to the official document. The costs come from additional tempdb space used for row versions and from traversing old row versions. These problems do...

I finally manage to make it work that way : public function testIsolationOK(){ $this->client->request('GET', self::WEB_SERVICES_EXISTING_REQUEST_URL); $this->setUp(); $this->client->request('DELETE', self::WEB_SERVICES_EXISTING_REQUEST_URL); } I don't know if it's a right way to do but it works. As a reminder here is the setUp method : protected function setUp(){ parent::setUp(); $this->client = static::createClient(); $this->entityManager =...

If TypeMock behaviours are bleeding between tests, then the first thing to check is that you're cleaning up between tests. You can do this explicitly by calling Isolater.CleanUp(), or using the preferred approach which is to decorate either the test methods or the test class itself with the [Isolated] attribute.