Skip to content

Update description for integration tests #48620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Apr 1, 2025
Merged

Update description for integration tests #48620

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 30 additions & 6 deletions contributing-docs/testing/integration_tests.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
-------------------------
Expand Down