Testing with Table-Driven Testing

When we’re writing tests for our command-line tool, we often want to write test cases that cover different variations of the function or tool usage. By doing this, we ensure that the different parts of our code are working, increasing the reliability of our tests and tool. For example, to test the filterOut() function from the walk tool, it’s a good idea to define test cases for the different conditions, such as filtering with or without extension, matching or not, and minimum size.

Creating the actions_test.go file

One of the benefits of Go is that we can use Go itself to write test cases. We don’t need a different language or external frameworks. By leveraging Go, we use all the language’s features to help define our test cases. A common pattern for writing test cases that cover different variations of the function of our testing is known as table-driven testing. In this type of testing, we define our test cases as a slice of anonymous struct, containing the data required to run our tests and the expected results.

We then iterate over this slice using loops ...