GO Testing and Benchmarking 2

Question 1

What is a table-driven test in Go?

Accepted Answer

A test that loops over a slice of input/output pairs to cover many cases in one function

Answer

Table-driven tests define a slice of structs with inputs and expected outputs, then loop over them with `t.Run` subtests for clear, concise coverage.

Question 2

What does `t.Run(name, func)` provide in Go testing?

Accepted Answer

Creates a named subtest that can be run independently and appears in test output

Answer

`t.Run` creates a named subtest, enabling structured test output, independent `-run` filtering, and parallel subtests via `t.Parallel()`.

Question 3

How do you write a benchmark function in Go?

Accepted Answer

Name it starting with `Benchmark` and take `*testing.B`

Answer

Benchmark functions follow `BenchmarkXxx(b *testing.B)` naming convention and are run with `go test -bench=.`.

Question 4

What is the significance of `b.N` in a Go benchmark?

Accepted Answer

The number of iterations the benchmark function should execute its inner loop

Answer

`b.N` is automatically adjusted by the benchmark framework until the benchmark runs long enough to produce a stable measurement; your loop must iterate `b.N` times.

Question 5

What does `go test -cover` report?

Accepted Answer

The percentage of statements executed during tests

Answer

`go test -cover` reports the percentage of Go source statements that were executed during the test run, giving a code coverage metric.

GO - Golang Online Test Practice Test

GO - Golang Online Test Practice Test

GO Testing and Benchmarking 2