Updates to automated tests doc (docker#3370)

* Updates to automated tests doc Updated automated test doc to reflect new autotest behavior. * made minor formatting changes Signed-off-by: Victoria Bialas <[email protected]>
sinacek · May 25, 2017 · 6457b5b · 6457b5b
1 parent 0a9866b
commit 6457b5b
Showing 1 changed file with 13 additions and 7 deletions.
diff --git a/docker-cloud/builds/automated-testing.md b/docker-cloud/builds/automated-testing.md
@@ -75,15 +75,21 @@ Docker repository, regardless of the Autotest settings.
 
     The following options are available:
 
-    * `Off`: No additional test builds. Tests only run if they're configured as part of an automated build.
-    * `Internal pull requests`: Run a test build for any pull requests to branches that match a build rule, but only when the pull request comes from the same source repository.
-    * `Internal and external pull requests`: Run a test build for any pull requests to branches that match a build rule, including when the pull request originated in an external source repository.
+    * `Off`: No additional test builds. Tests only run if they're configured
+    as part of an automated build.
+
+    * `Internal pull requests`: Run a test build for any pull requests
+    to branches that match a build rule, but only when the pull request comes
+    from the same source repository.
+
+    * `Internal and external pull requests`: Run a test build for any
+    pull requests to branches that match a build rule, including when the
+    pull request originated in an external source repository.
 
     > **Note**: For security purposes, autotest on _external pull requests_ is
-    disabled on public repositories. If you select this option on a public
-    repository, tests will still run on _internal_ pull requests (for example
-    from one branch into another inside the code repository) but not on for
-    external pull requests.
+    limited on public repositories. Private images will not be pulled and
+    environment  variables defined in Docker Cloud will not be
+    available. Automated builds will  continue to work as usual.
 
 9. Click **Save** to save the settings, or click **Save and build** to save and
 run an initial test.