You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2020/01/19 18:05:00 UTC

[jira] [Resolved] (AIRFLOW-4370) Testing: document “best practices” on dealing with Apache Airflow DAGs and operators

     [ https://issues.apache.org/jira/browse/AIRFLOW-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Potiuk resolved AIRFLOW-4370.
-----------------------------------
    Fix Version/s: 1.10.7
                   2.0.0
       Resolution: Fixed

> Testing: document “best practices” on dealing with Apache Airflow DAGs and operators
> ------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4370
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4370
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: breeze, documentation
>            Reporter: Aizhamal Nurmamat kyzy
>            Priority: Major
>              Labels: gsod2019
>             Fix For: 2.0.0, 1.10.7
>
>
> h4. Expected deliverables
>  * Introduction in testing workflows.
>  * A page for Designing and Testing DAGs
>  * Tips and working examples on “good practices” for designing DAGs
>  * Descriptions on how to perform dry-runs of DAGs
>  * Descriptions on how to write unit tests for DAGs
>  * Snippets with working examples of DAGs and tests for them. Use [PlantUML|https://github.com/plantuml/plantuml] diagrams to compliment all the new documentation
>  * How to develop operators that are testable?
> h4. Related resources
> [1] [https://github.com/jghoman/awesome-apache-airflow]
> [2] [https://airflow.apache.org/scheduler.html]
> [3] [https://github.com/PolideaInternal/airflow/blob/simplified-development-workflow/CONTRIBUTING.md]
> [4] [Airflow Breeze|https://github.com/PolideaInternal/airflow/blob/simplified-development-workflow/BREEZE.rst]
> [5] [https://github.com/godatadriven/whirl]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)