You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/07/19 08:04:00 UTC

[jira] [Updated] (AIRFLOW-4865) Use decorator to limit scope of config changes in tests

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

Ash Berlin-Taylor updated AIRFLOW-4865:
---------------------------------------
    Fix Version/s: 1.10.5

> Use decorator to limit scope of config changes in tests
> -------------------------------------------------------
>
>                 Key: AIRFLOW-4865
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4865
>             Project: Apache Airflow
>          Issue Type: Sub-task
>          Components: tests
>    Affects Versions: 2.0.0
>            Reporter: Ash Berlin-Taylor
>            Priority: Minor
>             Fix For: 1.10.5
>
>
> We have a number of cases where we change a config setting in our tests - right now we just do ` {{config.set()}} call.
> Most of the time these changes to config are not reverted, or are only reverted due the order that the tests run in, which is a bit fragile.
> We already have a tests/test_utils/decorators.py that contains a mock_conf_get decorator that we should use everywhere we need to change a config value in a test.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)