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, MichaelT, Ixrec, GlenH7 Sep 5 '15 at 13:06There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question. |
|||||||||
|
Personally, for each package I have one _test.go file with several test functions in (they must take the form I then test the return values and use One useful technique to help keep the test files smaller is to have a struct type called
and a function that sets up and returns a slice of initialised test data. You then only need to call Go has useful tools for testing including the very useful |
|||
|