From 4dafc3aa6d2ad1753c8e3a14fc4269f2d3aa10bb Mon Sep 17 00:00:00 2001 From: evan-danswer Date: Tue, 18 Mar 2025 21:14:05 -0700 Subject: [PATCH] Update README.md --- backend/tests/integration/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/backend/tests/integration/README.md b/backend/tests/integration/README.md index 414c8114d..5093d87e6 100644 --- a/backend/tests/integration/README.md +++ b/backend/tests/integration/README.md @@ -28,6 +28,14 @@ The idea is that each test can use the manager class to create (.create()) a "te pytest -s tests/integration/tests/path_to/test_file.py::test_function_name ``` +Running some single tests require the `mock_connector_server` container to be running. If the above doesn't work, +navigate to `backend/tests/integration/mock_services` and run +```sh +docker compose -f docker-compose.mock-it-services.yml -p mock-it-services-stack up -d +``` +You will have to modify the networks section of the docker-compose file to `_default` if you brought up the standard +onyx services with a name different from the default `onyx-stack`. + ## Guidelines for Writing Integration Tests - As authentication is currently required for all tests, each test should start by creating a user.