Question 1

go-testdeep vs testify which should I use?

Accepted Answer

go-testdeep is better for flexible, operator-based comparisons of complex data structures, while testify offers broader assertions and mocking capabilities. Choose go-testdeep if you need expressive partial matches, and testify for general-purpose testing with mocks.

Question 2

How to test HTTP APIs with go-testdeep?

Accepted Answer

Use the tdhttp helper to create a TestAPI instance, then chain methods like PostJSON and CmpJSONBody with JSON operators for validation. It handles automatic marshalling and allows embedded conditions like Between for dynamic fields.

Question 3

What operators are available in go-testdeep?

Accepted Answer

It supports over 50 operators including Between for ranges, Struct for partial matches, JSON for schema validation, and Smuggle for custom transformations. The full list is documented on the project's website.

Question 4

Is go-testdeep compatible with table-driven tests?

Accepted Answer

Yes, you can use td.Cmp or other functions within table-driven test loops, as it integrates with Go's standard testing package. Operators allow flexible assertions across multiple test cases.

Question 5

How to handle partial struct matching in go-testdeep?

Accepted Answer

Use the Struct operator with StructFields to specify which fields to match exactly and which to apply operators to, ignoring others. This enables focused comparisons without requiring full struct equality.

Question 6

Does go-testdeep support mocking or stubs?

Accepted Answer

No, go-testdeep focuses solely on comparison and validation; for mocking, you'd need to pair it with another library like testify/mock or gomock, as it doesn't provide built-in mocking features.

go-testdeep

What is go-testdeep?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions