GO Testing and Benchmarking

Question 1

What command runs all tests in the current Go module?

Accepted Answer

go test ./...

Answer

`go test ./...` recursively runs all test files in the current module, with `./...` matching all packages.

Question 2

What naming convention must a Go test function follow?

Accepted Answer

Must start with `Test` followed by a capital letter or underscore

Answer

Test functions must be named `TestXxx` where `Xxx` starts with an uppercase letter; they take a single `*testing.T` parameter.

Question 3

Which method on `*testing.T` marks a test as failed without stopping it?

Accepted Answer

t.Error()

Answer

`t.Error()` logs the failure message and marks the test as failed but continues executing the rest of the test function, unlike `t.Fatal()` which stops immediately.

Question 4

What does `t.Fatal()` do in a Go test?

Accepted Answer

Logs the message, marks the test as failed, and immediately stops the test function

Answer

`t.Fatal()` is equivalent to `t.Log()` followed by `t.FailNow()`, stopping the current test function immediately after logging the failure.

Question 5

What file suffix is required for Go test files?

Accepted Answer

_test.go

Answer

Go test files must end with `_test.go`; the `go test` tool recognizes and compiles these files only during testing, not in regular builds.

GO - Golang Online Test Practice Test

GO - Golang Online Test Practice Test

GO Testing and Benchmarking