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 2020/08/02 02:53:08 UTC
[airflow] branch master updated: Move Naming Conventions section in
CONTRIBUTING.rst (#10103)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/master by this push:
new 33646db Move Naming Conventions section in CONTRIBUTING.rst (#10103)
33646db is described below
commit 33646dbb7c804325db6055a0d95bc2ee41569e54
Author: Kamil BreguĊa <mi...@users.noreply.github.com>
AuthorDate: Sun Aug 2 04:52:10 2020 +0200
Move Naming Conventions section in CONTRIBUTING.rst (#10103)
---
CONTRIBUTING.rst | 39 +++++++++++++++++++--------------------
1 file changed, 19 insertions(+), 20 deletions(-)
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index d42ea8c..5486b53 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -665,27 +665,8 @@ If this function is designed to be called by "end-users" (i.e. DAG authors) then
...
# You SHOULD not commit the session here. The wrapper will take care of commit()/rollback() if exception
-Test Infrastructure
-===================
-
-We support the following types of tests:
-
-* **Unit tests** are Python tests launched with ``pytest``.
- Unit tests are available both in the `Breeze environment <BREEZE.rst>`_
- and `local virtualenv <LOCAL_VIRTUALENV.rst>`_.
-
-* **Integration tests** are available in the Breeze development environment
- that is also used for Airflow's CI tests. Integration test are special tests that require
- additional services running, such as Postgres, Mysql, Kerberos, etc.
-
-* **System tests** are automatic tests that use external systems like
- Google Cloud Platform. These tests are intended for an end-to-end DAG execution.
-
-For details on running different types of Airflow tests, see `TESTING.rst <TESTING.rst>`_.
-
-
Naming Conventions for provider packages
-========================================
+----------------------------------------
In Airflow 2.0 we standardized and enforced naming for provider packages, modules and classes.
those rules (introduced as AIP-21) were not only introduced but enforced using automated checks
@@ -746,6 +727,24 @@ The rules are as follows:
* System tests (not yet fully automated but allowing to run e2e testing of particular provider) are
named with _system.py suffix.
+Test Infrastructure
+===================
+
+We support the following types of tests:
+
+* **Unit tests** are Python tests launched with ``pytest``.
+ Unit tests are available both in the `Breeze environment <BREEZE.rst>`_
+ and `local virtualenv <LOCAL_VIRTUALENV.rst>`_.
+
+* **Integration tests** are available in the Breeze development environment
+ that is also used for Airflow's CI tests. Integration test are special tests that require
+ additional services running, such as Postgres, Mysql, Kerberos, etc.
+
+* **System tests** are automatic tests that use external systems like
+ Google Cloud Platform. These tests are intended for an end-to-end DAG execution.
+
+For details on running different types of Airflow tests, see `TESTING.rst <TESTING.rst>`_.
+
Metadata Database Updates
=========================