This is an automated email from the ASF dual-hosted git repository.
ferruzzi 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 909ff713a47 Random doc typos (#44750)
909ff713a47 is described below
commit 909ff713a47d6217592f919cddbbb6967e0fddf0
Author: D. Ferruzzi <[email protected]>
AuthorDate: Sat Dec 7 01:10:19 2024 -0800
Random doc typos (#44750)
* Random doc typos
* Update contributing-docs/testing/unit_tests.rst
Co-authored-by: Shahar Epstein <[email protected]>
* Update contributing-docs/testing/unit_tests.rst
---------
Co-authored-by: Shahar Epstein <[email protected]>
---
contributing-docs/testing/unit_tests.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/contributing-docs/testing/unit_tests.rst
b/contributing-docs/testing/unit_tests.rst
index 6c39b0780ed..12a2403b9a7 100644
--- a/contributing-docs/testing/unit_tests.rst
+++ b/contributing-docs/testing/unit_tests.rst
@@ -338,10 +338,10 @@ If your test accesses the database but is not marked
properly the Non-DB test in
How to verify if DB test is correctly classified
................................................
-When you add if you want to see if your DB test is correctly classified, you
can run the test or group
+If you want to see if your DB test is correctly classified, you can run the
test or group
of tests with ``--skip-db-tests`` flag.
-You can run the all (or subset of) test types if you want to make sure all ot
the problems are fixed
+You can run the all (or subset of) test types if you want to make sure all of
the problems are fixed
.. code-block:: bash
@@ -458,8 +458,8 @@ Do this:
Problems with Non-DB test collection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Sometimes, even if whole module is marked as ``@pytest.mark.db_test`` even
parsing the file and collecting
-tests will fail when ``--skip-db-tests`` is used because some of the imports
od objects created in the
+Sometimes, even if the whole module is marked as ``@pytest.mark.db_test``,
parsing the file and collecting
+tests will fail when ``--skip-db-tests`` is used because some of the imports
or objects created in the
module will read the database.
Usually what helps is to move such initialization code to inside the tests or
pytest fixtures (and pass
@@ -1086,9 +1086,9 @@ directly to the container.
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
+When you implement tests for providers, you should make sure that they are
compatible with older Airflow versions.
-Note that some of the tests if written without taking care about the
compatibility, might not work with older
+Note that some of the tests, if written without taking care about the
compatibility, might not work with older
versions of Airflow - this is because of refactorings, renames, and tests
relying on internals of Airflow that
are not part of the public API. We deal with it in one of the following ways:
