A few weeks ago, James Shore has published a novel idea in the area of automated testing. The “Nullable” testing patterns offer a way to incrementally write tests on legacy code and to avoid mocks and design changes for testability, by allowing any class, to implement in addition to the production code a “nullable” implementation that just outputs smart logging events.
Alex looks at this approach, at its goals, at its advantages and disadvantages, and reacts with a conclusion: is it worth looking into it? (Spoiler alert: it is).
The original article is here: https://www.jamesshore.com/v2/projects/nullables/testing-without-mocks
