golang-stretchr-testify

To write better Go tests with testify, use correct argument ordering—passing (expected, actual)—and prefer rich matchers like JSONEq or ElementsMatch to generate high-signal diffs that make test failures easy to diagnose.

Use require for test preconditions to stop execution immediately if a setup fails, and use assert for test verifications so multiple assertion failures are aggregated and reported together in your Go test suites.

Create mocks in Go by setting expectations with argument matchers and call modifiers, then always call AssertExpectations on your mock to verify all expected calls were made, preventing silent false positives.

Organize Go unit tests using testify/suite to group related tests, leveraging SetupTest for per-test initialization and shared setup and teardown methods to manage common test lifecycle state cleanly.

Handle async polling in Go tests using EventuallyWithT combined with CollectT, allowing you to make multiple assertions during polling without losing error context when the async condition fails.

When using testify for Go testing, you must pass *testing.T as the entry point and ensure proper mock verification; failing to use AssertExpectations or misusing require for verifications limits failure visibility.