Avoiding module mocks, building better interfaces, and preventing surprises while testing are crucial for creating effective and maintainable tests. This post highlights the downsides of excessive mocking of internal modules, and the benefits of testing through public interfaces. By following these principles, developers can reduce the risk of unexpected issues, and ensure that their tests remain relevant over time.

Continue reading

Author's picture

James Apple

Software Engineer

Sydney, Australia