You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2024/09/09 14:41:54 UTC
(airflow) branch main updated: fix indentation for unit test contribution docs (#42110)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 7c3dea44e7e fix indentation for unit test contribution docs (#42110)
7c3dea44e7e is described below
commit 7c3dea44e7e09e2450819d9e5954b1e45ec582d5
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Mon Sep 9 07:41:47 2024 -0700
fix indentation for unit test contribution docs (#42110)
The header levels in the unit test contribution docs have been
messed up.
---
contributing-docs/testing/unit_tests.rst | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/contributing-docs/testing/unit_tests.rst b/contributing-docs/testing/unit_tests.rst
index 9b4027843fa..5c1c2f1584d 100644
--- a/contributing-docs/testing/unit_tests.rst
+++ b/contributing-docs/testing/unit_tests.rst
@@ -1096,10 +1096,10 @@ can also decide to only run tests with ``-m quarantined`` flag to run only those
Compatibility Provider unit tests against older airflow releases
-................................................................
+----------------------------------------------------------------
Why we run provider compatibility tests
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.......................................
Our CI runs provider tests for providers with previous compatible airflow releases. This allows to check
if the providers still work when installed for older airflow versions.
@@ -1122,7 +1122,7 @@ taken that the tests implemented for providers in the sources allow to run it ag
of Airflow and against Airflow installed from PyPI package rather than from the sources.
Running the compatibility tests locally
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.......................................
Running tests can be easily done locally by running appropriate ``breeze`` command. In CI the command
is slightly different as it is run using providers build using wheel packages, but it is faster
@@ -1160,7 +1160,7 @@ directly to the container.
In such case you should follow the ``CI`` way of running the tests (see below).
Implementing compatibility for provider tests for older Airflow versions
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+........................................................................
When you implement tests for providers, you should make sure that they are compatible with older
@@ -1221,7 +1221,7 @@ are not part of the public API. We deal with it in one of the following ways:
top-level import into a local import, so that Pytest parser does not fail on collection.
Running provider compatibility tests in CI
-------------------------------------------
+..........................................
In CI those tests are run in a slightly more complex way because we want to run them against the build
provider packages, rather than mounted from sources.
@@ -1309,7 +1309,7 @@ This is run in order to check whether we are not using a feature that is not ava
older version of some dependencies.
Tests with lowest-direct dependency resolution for Airflow
-----------------------------------------------------------
+..........................................................
You can test minimum dependencies that are installed by Airflow by running (for example to run "Core" tests):
@@ -1338,7 +1338,7 @@ command as a sequence of downgrades like this:
Tests with lowest-direct dependency resolution for a Provider
--------------------------------------------------------------
+.............................................................
Similarly we can test if the provider tests are working for lowest dependencies of specific provider.
@@ -1381,7 +1381,7 @@ downgraded dependencies will contain both Airflow and Google Provider dependenci
How to fix failing lowest-direct dependency resolution tests
-------------------------------------------------------------
+............................................................
When your tests pass in regular test, but fail in "lowest-direct" dependency resolution tests, you need
to figure out the lower-bindings missing in ``hatch_build.py`` (for Airflow core dependencies) or