Browse code

cleanup test-integration

Signed-off-by: Jessica Frazelle <princess@docker.com>

Jessica Frazelle authored on 2015/05/13 07:39:57
Showing 2 changed files
... ...
@@ -68,10 +68,6 @@ is simply `test`. The make file contains several targets for testing:
68 68
     <td>Run just the unit tests.</td>
69 69
   </tr>
70 70
   <tr>
71
-    <td class="monospaced">test-integration</td>
72
-    <td>Run just integration tests.</td>
73
-  </tr>
74
-  <tr>
75 71
     <td class="monospaced">test-integration-cli</td>
76 72
     <td>Run the test for the integration command line interface.</td>
77 73
   </tr>
... ...
@@ -143,7 +139,7 @@ Try this now.
143 143
 
144 144
 3. Run the tests using the `hack/make.sh` script.
145 145
 
146
-        root@5f8630b873fe:/go/src/github.com/docker/docker# hack/make.sh dynbinary binary cross test-unit test-integration test-integration-cli test-docker-py
146
+        root@5f8630b873fe:/go/src/github.com/docker/docker# hack/make.sh dynbinary binary cross test-unit test-integration-cli test-docker-py
147 147
 
148 148
     The tests run just as they did within your local host.
149 149
 
... ...
@@ -54,7 +54,7 @@ RELEASE_BUNDLES=(
54 54
 
55 55
 if [ "$1" != '--release-regardless-of-test-failure' ]; then
56 56
 	RELEASE_BUNDLES=(
57
-		test-unit test-integration
57
+		test-unit
58 58
 		"${RELEASE_BUNDLES[@]}"
59 59
 		test-integration-cli
60 60
 	)