From 6696aa76f48bac835d577de51579d983cce9d3f9 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Tue, 1 Apr 2025 13:37:29 +0200 Subject: [PATCH] Update description for integration tests When we split tests into core and provider tests, the description of integration tests running has not been updated to reflect the split. This PR fixes it. --- .../testing/integration_tests.rst | 36 +++++++++++++++---- 1 file changed, 30 insertions(+), 6 deletions(-) diff --git a/contributing-docs/testing/integration_tests.rst b/contributing-docs/testing/integration_tests.rst index ea9dfb7e9529a..3be9f60a17a65 100644 --- a/contributing-docs/testing/integration_tests.rst +++ b/contributing-docs/testing/integration_tests.rst @@ -45,7 +45,13 @@ NOTE: Every integration requires a separate container with the corresponding int These containers take precious resources on your PC, mainly the memory. The started integrations are not stopped until you stop the Breeze environment with the ``breeze down`` command. -The following integrations are available: +While you can run ``breeze`` or ``breeze shell` with one or multiple integrations enabled, some integrations +are pure "provider" integrations, and some are "core" integration. Which means that some of the integrations +have tests defined in the "providers" tests (because they are testing provider features), but other +integrations are testing core features of Airflow (Fore example executors with CeleryExecutor). + +The following integrations are available ("Core tests ?" column indicates if the integration is a +core or provider type of test. .. BEGIN AUTO-GENERATED INTEGRATION LIST @@ -170,19 +176,37 @@ Here is an example of the collection limited to the ``providers/apache`` sub-dir Running Integration Tests from the Host --------------------------------------- -You can also run integration tests using Breeze from the host. +You can also run integration tests using Breeze from the host. Depending on the type of integration, +you can rum "providers" or "core" integration tests. You can consult the table above to see which +integration is "core" and which is "provider" one, also by running the +``breeze providers-integration-tests --help`` or ``breeze core-integration-tests --help`` command +you can see the list of available integrations for each type of test. + +Runs all core integration tests: + + .. code-block:: bash + + breeze testing core-integration-tests --db-reset --integration all-testable -Runs all integration tests: +Runs all providers integration tests: .. code-block:: bash - breeze testing integration-tests --db-reset --integration all-testable + breeze testing providers-integration-tests --db-reset --integration all-testable + + +Runs mongo providers integration tests: + + .. code-block:: bash + + breeze testing providers-integration-tests --db-reset --integration mongo + -Runs all mongo DB tests: +Runs kerberos core integration tests: .. code-block:: bash - breeze testing integration-tests --db-reset --integration mongo + breeze testing core-integration-tests --db-reset --integration kerberos Writing Integration Tests -------------------------