You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kaxil Naik (JIRA)" <ji...@apache.org> on 2019/01/12 12:45:00 UTC
[jira] [Resolved] (AIRFLOW-3680) Test naming/structure
inconsistencies in GCP operators
[ https://issues.apache.org/jira/browse/AIRFLOW-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaxil Naik resolved AIRFLOW-3680.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.10.2
> Test naming/structure inconsistencies in GCP operators
> ------------------------------------------------------
>
> Key: AIRFLOW-3680
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3680
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Jarek Potiuk
> Assignee: Jarek Potiuk
> Priority: Major
> Fix For: 1.10.2
>
>
> The GCP-related operators were evolving over time and the approach to implement those
> have changed over time. After some 30+ operators implemented, it's time
> to introduce some consistency across all the operators. Not changing the logic of the operators - but rather make sure tests for them use consistent naming and can be run in the same way - including Unit tests and System tests talking to real GCP project/services.
> Those are:
> * Separating out System test cases from Unit test cases
> * Consistent names of variables that are used in system test cases
> * Updated documentation to be consistent across the operators
> * Updated examples to be better readable and runnable as System Tests
> * Added helper methods that allow to make setUp/tearDown for System Tests
> The test impacted are for the following operators:
> * Bigtable
> * Compute
> * ComputeIgm
> * Function
> * Spanner
> * CloudSql
> * CloudSqlQuery
> * S3ToGcs
> * BigQuery
> * Container
> * Dataproc
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)