-8

I am new to golang and RunC and now doing some research on it as a part of my intership. What kind of contents do the ' _test.go ' functions check during testing a program or a container with Golang (Or RunC in case of Docker containers)? Can someone please explain me the testing process?

closed as too broad by gnat, durron597, user40980, Ixrec, user53019 Sep 5 '15 at 13:06

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

-1

Personally, for each package I have one _test.go file with several test functions in (they must take the form func TestX(t *testing.T)). Each of these test functions runs through all of my regular functions in the package, passing in acceptable data, extreme data (data on the boundaries of acceptable), and invalid data (passing nil in, etc.).

I then test the return values and use t.Log() to print useful output. If your code doesn't behave how it is supposed to, you can use t.Fail() to cause the test to fail, or t.Errorf()to log an error message and then fail.

One useful technique to help keep the test files smaller is to have a struct type called testData or something like that, with a field for:

  • An instance of the data you will pass in.
  • Each expected return value from various functions.

and a function that sets up and returns a slice of initialised test data.

You then only need to call td := setupTestData(), and loop through each member, passing in and testing the same fields.

Go has useful tools for testing including the very useful cover tool. Open terminal or command prompt in the package directory and do go tool cover -html="cover.out" to see a visual representation of how much of your code is covered by your test.

Not the answer you're looking for? Browse other questions tagged or ask your own question.