golang-testing

Table-driven tests in Go use t.Run to execute subtests, allowing structured iteration over test cases. You define test cases in a slice and loop through them, passing each case to t.Run for isolated execution and clear failure reporting.

Use t.Helper to mark test utility functions so failures point to the caller, and t.Parallel to signal that a test can run concurrently. They improve error readability and reduce execution time for independent test cases.

Require stops test execution immediately on failure, while assert records the failure and continues. Use require for conditions that make subsequent assertions meaningless, and assert to collect multiple failure results in one test.

Test fixtures in Go are managed using a testdata directory, storing input files and expected outputs. This convention keeps test resources organized and accessible, ensuring compatibility across different Go releases.

Go benchmarks use functions prefixed with Benchmark to measure performance. They execute repeatedly to gather stable timing data, helping identify regressions and optimize code paths within table-driven test structures.

Yes, testify assertions integrate seamlessly with table-driven Go tests. You can use require and assert within t.Run subtests to enforce deterministic failures and clear messaging for each test case iteration.