ashb opened a new pull request #18432:
URL: https://github.com/apache/airflow/pull/18432


   - test_render_template_fields_native_envs duplicated the existing
     test_retest_render_template_with_native_envs
   - Testing dag settings (user_defined_*) was testing the behaviour of
     Jinja2. The test has bee streamlined and moved to test_dag (where the
     jinija env is created)
   - Tests of the undefined behaviour have been removed as it is just
     testing Jinja behaviour, moved to just testing property of env in
     test_dag.
   - Removed neededless DAG creation
   - Used BaseOperator instead of DummyOperator
   - Used existing MockOperator class instead of file-local CustomOp
   
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).


-- 
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