Table-Driven Tests

The same test logic applied to a dozen different inputs is the most common shape a Go test takes. Copy-pasting that logic for each case bloats the file and hides the actual variation behind boilerplate. Table-driven tests collapse the repetition into a slice of cases, leaving one loop that runs them all and one place to add the next case. This chapter covers the pattern, the naming conventions, the failure-reporting tricks that make it usable in practice, and the cases where reaching for a table is the wrong call.