This is an automated email from the ASF dual-hosted git repository.
shahar pushed a commit to branch v2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v2-10-test by this push:
new b5f033a933d [v2-10-test] Random doc typos (#44750) (#44758)
b5f033a933d is described below
commit b5f033a933d6bba2433a50a62b389b6546123ac4
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Sat Dec 7 12:14:14 2024 +0200
[v2-10-test] Random doc typos (#44750) (#44758)
* Random doc typos
* Update contributing-docs/testing/unit_tests.rst
* Update contributing-docs/testing/unit_tests.rst
---------
(cherry picked from commit 909ff713a47d6217592f919cddbbb6967e0fddf0)
Co-authored-by: D. Ferruzzi <[email protected]>
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 c83f391e528..ccd38250424 100644
--- a/contributing-docs/testing/unit_tests.rst
+++ b/contributing-docs/testing/unit_tests.rst
@@ -378,10 +378,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
@@ -502,8 +502,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
@@ -1162,9 +1162,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:
