[DOCS] Extension on System Tests, documenting dag.test() #59390
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
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
Closed
2 tasks
juditnovak
force-pushed
the
docs/system_tests_extend
branch
from
255dfbc to
e2abd73
Compare
juditnovak
commented
Dec 13, 2025
| conf.read_file(open(f"{YOUR_TEST_CONFIG_FILE}")) | ||
| Custom configuraion allows an easy way to load numerous custom options at once (typically ones that may correspond | ||
| to custom providers). |
Contributor
Author
There was a problem hiding this comment.
I have drafted Proposal #59389 that may allow for handier way to do this. However I understand the strong protection within the Airflow testuite to avoid any interference across deployments, thus I understand that such a change may not be deseired.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documentaiton extensions
This draft came to existence as a follow-up on the conversation on Issue #59074 , based on the experience of using Airflow Pytest plugin and Airflow System tests with custom Airflow Executor and custom Airflow Operatros/Decorators.
The content is very raw, it's more just a "proof of concept" in its current stage.
In case any I didn't find the correct way to achieve certain targets, please let me know. I did my best to find the right solution at each step building my test workflows, however on occasions I couldn't find a more elegant solution (perhaps by my mistake) than documented here. I'm grateful for highlights on those areas, and of course modify the draft accordingly.