From 58de6277821698a2f97d1a0c83664ab34ff2e8d8 Mon Sep 17 00:00:00 2001 From: Daniel Nephin Date: Thu, 15 Mar 2018 14:30:35 -0400 Subject: [PATCH] Update testing doc Signed-off-by: Daniel Nephin --- TESTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TESTING.md b/TESTING.md index 20f7c9254e..1231e1c5f4 100644 --- a/TESTING.md +++ b/TESTING.md @@ -8,11 +8,11 @@ questions you may have as an aspiring Moby contributor. Moby has two test suites (and one legacy test suite): * Unit tests - use standard `go test` and - [testify](https://github.com/stretchr/testify) assertions. They are located in + [gotestyourself/assert](https://godoc.org/github.com/gotestyourself/gotestyourself/assert) assertions. They are located in the package they test. Unit tests should be fast and test only their own package. * API integration tests - use standard `go test` and - [testify](https://github.com/stretchr/testify) assertions. They are located in + [gotestyourself/assert](https://godoc.org/github.com/gotestyourself/gotestyourself/assert) assertions. They are located in `./integration/` directories, where `component` is: container, image, volume, etc. These tests perform HTTP requests to an API endpoint and check the HTTP response and daemon state after the call.