Mockey

Why it's ranked here

Its strongest case is practical reach: it handles ordinary, generic, and variadic code, methods, variables, conditional behavior, sequences, and scoped cleanup. That breadth comes with a serious caveat. It changes executable instructions and requires special compiler flags, so it suits controlled test builds better than routine dependency injection.

What's good

Scoped lifecycle helpers automatically restore replacements and support nesting, which reduces cleanup mistakes. Hooks may preserve access to the original implementation. Signature and return checks catch mismatches. Advanced controls include call counts, goroutine targeting, conditional behavior, sequential results, and support for difficult unexported methods.

Tradeoffs

Tests must disable inlining and compiler optimization, otherwise replacements may fail. The implementation depends on unsafe memory access, instruction disassembly, runtime internals, and architecture-specific behavior. Manual restoration must follow last-in, first-out order in some generic cases or crashes may occur. Interface mocking remains experimental.

How to use it well

Use it for Go unit tests around legacy or tightly coupled code where introducing interfaces would be disproportionate. Keep replacements inside scoped lifecycle blocks and compile tests with the required flags. Prefer the lightweight scope helper unless you want GoConvey integration. Mockey does not replace an assertion or test-organization framework.

Observed

License

Apache License 2.0

Primary language

Go

Install surface

Go module installed with go get from github.com/bytedance/mockey

Interface

Imported Go testing library

Operating systems

Darwin, Linux, and Windows

Architectures

AMD64 and ARM64

Module declaration

go.mod declares Go 1.18

Test structure

Repository text includes an internal monkey patch test file