vincbeck opened a new pull request, #40205: URL: https://github.com/apache/airflow/pull/40205
`Dag.test()` allows testing a DAG locally. [See documentation](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/debug.html#testing-dags-with-dag-test). `Dag.test()` uses no scheduler and no executor to run the task. It runs just all the task instances of the DAG in the current process. This PR extends `Dag.test()` functionality to add capability of testing a DAG in an executor. If a different executor than `LocalExecutor` is configured in config, then it will use this executor to run the DAG. By default, `pytest` erases all environment variables before executing tests, thus I introduced a new flag to disable this behavior if desired: `--keep-env-variables`. For example, the command below executes successfully the system test `tests/system/providers/amazon/aws/example_sns.py` with a different executor than `LocalExecutor`. Here my Airflow environment was configured to use `AwsEcsExecutor` but it could have been another one. `breeze testing tests tests/system/providers/amazon/aws/example_sns.py --system amazon --keep-env-variables --test-type System --forward-credentials --test-timeout 500`. <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- 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 an 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/ --> <!-- Please keep an empty line above the dashes. --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
