Testing In Go

Table-driven tests, testify, subtests, benchmarking (testing.B).

Why we need this / what value this brings

Table-driven tests are the dominant idiom and read very differently from xUnit-style test classes.

When to use this

Any new package — Go's testing culture expects tests alongside the code, not bolted on after.

How to use or implement this

go test -bench for performance-sensitive code, table-driven tests as the default shape.

Research questions

• (add as research surfaces open questions)

---

Empty folder — drop notes, links, and findings here as you research.