Only sut service and its dependents are started (#3426)

* Only `sut` service and its dependents are started

* re-worded a few sentences

Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
This commit is contained in:
Wilfred van der Deijl
2017-05-31 02:09:50 +02:00
committed by Victoria Bialas
parent b12ec60faa
commit 5b6345c5cf

View File

@@ -35,11 +35,19 @@ The example above builds the repository, and runs the `run_tests.sh` file inside
a container using the built image.
You can define any number of linked services in this file. The only requirement
is that `sut` is defined. Its return code determines if tests passed or not:
tests **pass** if the `sut` service returns `0`, and **fail** otherwise.
is that `sut` is defined. Its return code determines if tests passed or not.
Tests **pass** if the `sut` service returns `0`, and **fail** otherwise.
> **Note**: Only the `sut` service and all other services listed in `depends_on`
are started. For instance, if you have services that poll for changes in other
services, be sure to include the polling services in the `depends_on` list to
make sure all of your services start.
You can define more than one `docker-compose.test.yml` file if needed. Any file
that ends in `.test.yml` is used for testing, and the tests run sequentially. You can also use [custom build hooks](advanced.md#override-build-test-or-push-commands) to further customize your test behavior.
that ends in `.test.yml` is used for testing, and the tests run sequentially.
You can also use [custom build
hooks](advanced.md#override-build-test-or-push-commands) to further customize
your test behavior.
> **Note**: If you enable Automated builds, they will also run any tests defined
in the `test.yml` files.