This is an automated email from the ASF dual-hosted git repository.
vatsrahul1001 pushed a commit to branch v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-3-test by this push:
new 1e07bdae52f Fix sphinx build error (#69505) (#70761)
1e07bdae52f is described below
commit 1e07bdae52ff9010b8ff3fc2daac58753313784a
Author: Rahul Vats <[email protected]>
AuthorDate: Thu Jul 30 19:31:33 2026 +0530
Fix sphinx build error (#69505) (#70761)
(cherry picked from commit 6bba9b65d39d67030a526220253a0c643919ea24)
Co-authored-by: Wei Lee <[email protected]>
---
airflow-core/docs/best-practices.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/airflow-core/docs/best-practices.rst
b/airflow-core/docs/best-practices.rst
index 2a3be332d16..724398c9f82 100644
--- a/airflow-core/docs/best-practices.rst
+++ b/airflow-core/docs/best-practices.rst
@@ -852,7 +852,7 @@ You can use environment variables to parameterize the Dag.
Mocking variables and connections
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-When you write tests for code that uses variables or a connection, you must
ensure that they exist when you run the tests. The obvious solution is to save
these objects to the database so they can be read while your code is executing.
However, reading and writing objects to the database are burdened with
additional time overhead. In order to speed up the test execution, it is worth
simulating the existence of these objects without saving them to the database.
For this, you can create env [...]
+When you write tests for code that uses variables or a connection, you must
ensure that they exist when you run the tests. The obvious solution is to save
these objects to the database so they can be read while your code is executing.
However, reading and writing objects to the database are burdened with
additional time overhead. In order to speed up the test execution, it is worth
simulating the existence of these objects without saving them to the database.
For this, you can create env [...]
For variable, use :envvar:`AIRFLOW_VAR_{KEY}`.
