mock-generation

Generate typed Go test doubles by applying a five-type taxonomy to isolate unmanaged dependencies. This ensures compile-time interface compliance and refactor-safe test suites using automated generation tools like mockery, gomock, or moq.

In Go mocking, stubs return predefined data, spies record interactions, and fakes provide working in-memory implementations. Selecting the correct test double type ensures you avoid over-mocking and prevent coupling your tests to internal implementation details.

Yes, mockery and gomock work with the Classical school of testing by isolating only unmanaged dependencies. This standardized approach prevents implementation-detail coupling and ensures your test suite remains maintainable during refactoring.

You should not use mocks in Go unit testing for managed dependencies that can be tested with real implementations. Over-mocking managed dependencies creates brittle tests that break during refactoring and couple your test suite to internal implementation details.

Automate mock generation in Go by using industry-standard tools like mockery, gomock, or moq to enforce compile-time interface compliance. This eliminates hand-written mocks and ensures type-safe test doubles that resist breaking during refactoring.