Signed-off-by: Daniel Nephin <dnephin@docker.com>
Daniel Nephin authored on 2018/03/16 03:30:35... | ... |
@@ -8,11 +8,11 @@ questions you may have as an aspiring Moby contributor. |
8 | 8 |
Moby has two test suites (and one legacy test suite): |
9 | 9 |
|
10 | 10 |
* Unit tests - use standard `go test` and |
11 |
- [testify](https://github.com/stretchr/testify) assertions. They are located in |
|
11 |
+ [gotestyourself/assert](https://godoc.org/github.com/gotestyourself/gotestyourself/assert) assertions. They are located in |
|
12 | 12 |
the package they test. Unit tests should be fast and test only their own |
13 | 13 |
package. |
14 | 14 |
* API integration tests - use standard `go test` and |
15 |
- [testify](https://github.com/stretchr/testify) assertions. They are located in |
|
15 |
+ [gotestyourself/assert](https://godoc.org/github.com/gotestyourself/gotestyourself/assert) assertions. They are located in |
|
16 | 16 |
`./integration/<component>` directories, where `component` is: container, |
17 | 17 |
image, volume, etc. These tests perform HTTP requests to an API endpoint and |
18 | 18 |
check the HTTP response and daemon state after the call. |