Go Testing

How a Go test is written, in every repo. What to test is the repo's testing-policy when it ships one: the kinds of test it uses, what each is worth, which a feature needs, and the reusable patterns to copy as the codebase grows. It never restates how a test is written, so the two do not overlap. A repo without one gets it from testing-policy-creator. For the red-green-refactor loop, use tdd.

Your defaults that are wrong here

These are the habits that show up unprompted. Check your test against this table before writing it, and again before finishing, because they creep back in late in a long task.