https://github.com/lukaslangen/workshop-unittesting-presentation/blob/main/presentation.md#module-2-organizing-tests-1

DoubleFactories have shown to be not as practical as I initially thought. Today I prefer to have multiple classes as test doubles for doubles that are not provided by phpunit and using phpunit stubs and mocks in the test itself.

To stick with the example of the module it would look like this:

tests/Doubles/Repository
  | - RepositoryDummy.php
  | - RepositoryFake.php
  | - RepositorySpy.php

The text at https://github.com/lukaslangen/workshop-unittesting-presentation/blob/main/presentation.md#module-2---test-doubles-6 speaks about an expectation that a method is called exactly twice, while the example code says $this->exactly(3) instead.