Support running airflow dags test from local files
#50420
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, we can't run `airflow dags test` in isolation with a local dag file. We need to first run `airflow dags reserialize`, so DAGs are parsed and stored in DB, because the `airflow dags test` currently loads it from DB. The change in this PR/commit allows testing DAGs from different sources: - Using bundle configuration (`--bundle-name`) - Using direct file path (`--dagfile-path`/`-f`) - Using default behavior (from DB) This speeds up the process too since we don't have to load the entire DagBag to run a single file.
kaxil
force-pushed
the
dag-test-improvements
branch
from
6431b45 to
f44180b
Compare
Member
Member
Author
Lee-W
approved these changes
May 10, 2025
bugraoz93
approved these changes
May 10, 2025
Co-authored-by: Wei Lee <weilee.rx@gmail.com>
kaxil
added a commit
that referenced
this pull request
May 12, 2025
Currently, we can't run `airflow dags test` in isolation with a local dag file. We need to first run `airflow dags reserialize`, so DAGs are parsed and stored in DB, because the `airflow dags test` currently loads it from DB. The change in this PR/commit allows testing DAGs from different sources: - Using bundle configuration (`--bundle-name`) - Using direct file path (`--dagfile-path`/`-f`) - Using default behavior (from DB) This speeds up the process too since we don't have to load the entire DagBag to run a single file. (cherry picked from commit 7b0063b)
kaxil
added a commit
that referenced
this pull request
Jun 3, 2025
Currently, we can't run `airflow dags test` in isolation with a local dag file. We need to first run `airflow dags reserialize`, so DAGs are parsed and stored in DB, because the `airflow dags test` currently loads it from DB. The change in this PR/commit allows testing DAGs from different sources: - Using bundle configuration (`--bundle-name`) - Using direct file path (`--dagfile-path`/`-f`) - Using default behavior (from DB) This speeds up the process too since we don't have to load the entire DagBag to run a single file. (cherry picked from commit 7b0063b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, we can't run
airflow dags testin isolation with a local dag file. We need to first runairflow dags reserialize, so DAGs are parsed and stored in DB, because theairflow dags testcurrently loads it from DB.The change in this PR/commit allows testing DAGs from different sources:
--bundle-name)--dagfile-path/-f)This speeds up the process too since we don't have to load the entire DagBag to run a single file.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.