From eca84e56c2a94be59e7023731c54d7d9feebf545 Mon Sep 17 00:00:00 2001 From: Andrew Glaude Date: Wed, 13 Dec 2023 14:19:41 -0500 Subject: [PATCH] readme: Add example for running just one integration container (#2429) --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 36b3d7bcfc..47a7ece6d2 100644 --- a/README.md +++ b/README.md @@ -99,4 +99,10 @@ might be running versions different from the vendored one, creating hard to debu To run integration tests locally, you should set the `INTEGRATION` environment variable. The dependencies of the integration tests are best run via Docker. To get an idea about the versions and the set-up take a look at our [docker-compose config](./docker-compose.yaml). -The best way to run the entire test suite is using the [test.sh](./test.sh) script. You'll need Docker and docker-compose installed. Run `./test.sh --all` to run all of the integration tests through the docker-compose environment. Run `./test.sh --help` for more options. \ No newline at end of file +The best way to run the entire test suite is using the [test.sh](./test.sh) script. You'll need Docker and docker-compose installed. Run `./test.sh --all` to run all of the integration tests through the docker-compose environment. Run `./test.sh --help` for more options. + +If you're only interested in the tests for a specific integration it can be useful to spin up just the required containers via docker-compose. +For example if you're running tests that need the `mysql` database container to be up: +```shell +docker compose -f docker-compose.yaml -p dd-trace-go up -d mysql +``` \ No newline at end of file