How can you keep tests isolated when the SUT relies on global state?
By shifting the dependency to in-memory with a Fake Test Double.
How can you make it clear which dependencies affect the behavior under test and which don’t?
By using a Dummy Test Double that doesn’t do anything to replace those dependencies that do not affect the behavior.
We already learned about Test Doubles, “test-specific equivalents” of the system under test dependencies, and how to use two of them. Stubs control the SUT inputs (Chapter 8 and Chapter 10), and Spies record the ...
