Daniel Canter b5e1b8f619 Use t.Run for /pkg/cri tests ... A majority of the tests in /pkg/cri are testing/validating multiple things per test (generally spec or options validations). This flow lends itself well to using *testing.T's Run method to run each thing as a subtest so `go test` output can actually display which subtest failed/passed. Some of the tests in the packages in pkg/cri already did this, but a bunch simply logged what sub-testcase was currently running without invoking t.Run. Signed-off-by: Daniel Canter <dcanter@microsoft.com>		2022-05-29 18:32:09 -07:00
..
container_io.go	[CRI] Reduce clutter of log entries during process execution	2021-01-06 13:09:03 -05:00
exec_io.go	[CRI] Reduce clutter of log entries during process execution	2021-01-06 13:09:03 -05:00
helpers_unix.go	Replace golang.org/x/net/context with std library	2022-02-22 02:27:05 +08:00
helpers_windows.go	Replace golang.org/x/net/context with std library	2022-02-22 02:27:05 +08:00
helpers.go	Replace golang.org/x/net/context with std library	2022-02-22 02:27:05 +08:00
logger_test.go	Use t.Run for /pkg/cri tests	2022-05-29 18:32:09 -07:00
logger.go	refactor: move from io/ioutil to io and os package	2021-09-21 09:50:38 +08:00