In the landscape of software testing, the choice between a do-it-yourself (DIY) approach to mocking and utilizing mocking frameworks is a pivotal decision for programmers. While mocking is indispensable for code reliability, its overuse or incorrect implementation can introduce complexities and fragilities within test suites. This article navigates the balance between leveraging mocks effectively and avoiding common pitfalls, including the dangers of writing mocks in a suboptimal manner.
This is bad advice. Mocking libraries have come from many years of experience. Rolling your own test library will be like reinventing the wheel, but with less documentation and more inconsistencies.