testdouble / contributing-tests Goto Github PK

In https://github.com/testdouble/contributing-tests/wiki/London-school-TDD, the last chapter Increased refactoring cost, the second paragraph has an unfinished sentence: In general, attempting to refactor the implementation without changing the test first

The definition of partial mock on the Partial Mock page:

Put simply, "partial mock" refers to any actual object which has been wrapped or changed to provide artificial responses or verify actual interactions by a test.

I already have a good intuitive understanding of partial mocks and am thinking about how I'd present them to a beginner. I think this part of the definition could be improved:

provide artificial responses or verify actual interactions by a test.

Partial mocks provide artificial responses to some methods and real responses for others. As a result they can or cannot verify actual interactions by a test depending on the method. This is what's bad about them. Theoretically you could construct a partial mock using a mocking library or handrolled but override all the methods with artificial responses. In that case I don't know if it is still considered a partial mock. If so, I can see how creating both an accurate and understandable definition for beginners would be hard.

I'd prefer this definition

Put simply, "partial mock" refers to any actual object which has been wrapped or changed to provide artificial responses to some methods but not others

Hi @searls ,

some time ago I've watched yours Game of Life series and finally landed here – thanks for the effort! I'm just curious about the intention of Test Pyramid comments, especially the one concerning integration tests (or something between E2E and units). In particular, where would you classify testing collaborations? Or perhaps the meaning is: do not couple the test with particular framework or more general, a piece of code that I don't own?