Aaron Lehmann 6052f2b396 Remove pkg/testutil/assert in favor of testify ... I noticed that we're using a homegrown package for assertions. The functions are extremely similar to testify, but with enough slight differences to be confusing (for example, Equal takes its arguments in a different order). We already vendor testify, and it's used in a few places by tests. I also found some problems with pkg/testutil/assert. For example, the NotNil function seems to be broken. It checks the argument against "nil", which only works for an interface. If you pass in a nil map or slice, the equality check will fail. In the interest of avoiding NIH, I'm proposing replacing pkg/testutil/assert with testify. The test code looks almost the same, but we avoid the confusion of having two similar but slightly different assertion packages, and having to maintain our own package instead of using a commonly-used one. In the process, I found a few places where the tests should halt if an assertion fails, so I've made those cases (that I noticed) use "require" instead of "assert", and I've vendored the "require" package from testify alongside the already-present "assert" package. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2017-04-14 12:03:21 -07:00
..
command	Remove pkg/testutil/assert in favor of testify	2017-04-14 12:03:21 -07:00
compose	Remove pkg/testutil/assert in favor of testify	2017-04-14 12:03:21 -07:00
config	Add label filter for docker system prune	2017-04-06 09:11:25 -07:00
debug	Move debug functions to cli/debug package	2016-12-12 09:33:58 +01:00
flags	Remove pkg/testutil/assert in favor of testify	2017-04-14 12:03:21 -07:00
internal/test	Added unit tests to the cli/command/idresolver package	2017-04-07 23:23:39 -04:00
trust	Replace fmt.Errorf() with errors.Errorf() in the cli	2017-03-24 16:58:07 -04:00
cobra.go	Replace fmt.Errorf() with errors.Errorf() in the cli	2017-03-24 16:58:07 -04:00
error.go
required.go	Replace fmt.Errorf() with errors.Errorf() in the cli	2017-03-24 16:58:07 -04:00