3 Fighting with Complexity

Question 1

How to you mark a function as a test helper?

Answer 1

Include a call to t.Helper() in the function.

Question 2

What does t.Helper() do?

Answer 2

The caller, instead of the helper, will report the failure.

Question 3

What is the idiomatic solution to the duplicate tests problem?

Answer 3

table-driven testing.

Question 4

What are the advantages of table-driven-testing?

Answer 4

• Less code
• Less cognitive load
• Easy to add new test cases
• Easier to see corner cases are covered
• Avoids adding helper methods for shared logic

Question 5

What is a test that you can run within a top-level test function in isolation?

Answer 5

A subtest.

Question 6

What Go command runs tests and shuffles the order they run in?

Answer 6

go test -v -shuffle=on

Question 7

After running a shuffled test how to I rerun again in that same order?

Answer 7

Take the number output in the first run and use it with the shuffle flag.

go test -v -shuffle=1624629565232133000

Question 8

How do I run a subtest?

Answer 8

t.Run(name string, func (t *testing.T) {…} )

Question 9

What is a higher order function?

Answer 9

a function that returns another function.

Question 10

Declare a table test who’s subtest would be run in random order?

Answer 10

Use a map instead of an array struct.
~~~
tests := map[string]struct{..}
~~~