mnojek opened a new pull request #22311:
URL: https://github.com/apache/airflow/pull/22311


   Hello everyone,
   
   I am really excited to show you the collective work of the last few weeks!
   This is the initial PR that prepares Airflow to be compliant with
   
[AIP-47](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-47+New+design+of+Airflow+System+Tests)
 which is related to the new design of system tests in Airflow. This is the 
first step to automated system tests in our CI. When it is merged, it will 
enable other providers to start migration of their system tests to the new 
design.
   
   Basically, the main advantage of this design is that we will have 
self-contained tests encapsulated in DAGs that can be run with pytest as well 
as just imported into Airflow and be executed there. Requirements for the 
environment are kept at minimum and are mostly related to specific test needs. 
By using built-in features of Airflow, each system test is a DAG that is also 
an example of usage for tested Operator. All in one, in a simple file :)
   
   It is a minimal PR that contains a bunch of tests for only 1 Google service 
(BigQuery) and everything else that is required by the tests to be working 
properly. It also consists of all necessary documentation, new pre-commit hook 
(`check-watcher-in-examples`), updated checks (in `tests/always`) and some 
other things. More tests will be migrated in a separate PRs, because we wanted 
this one to be as small as possible.
   
   Please familiarize with the changes and also read the AIP-47 to fully 
understand why they are needed.
   We really want to hear your feedback. In case of any questions, concerns or 
comments - we are here to answer them and explain things. The whole work was 
overseen by @potiuk and done together with @bhirsz and @kosteev and me 
(@mnojek).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to