Guard provider-dependent tests in airflow-core for standalone core testing#63572
Draft
ShubhamGondane wants to merge 3 commits intoapache:mainfrom
Draft
Guard provider-dependent tests in airflow-core for standalone core testing#63572ShubhamGondane wants to merge 3 commits intoapache:mainfrom
ShubhamGondane wants to merge 3 commits intoapache:mainfrom
Conversation
…ses without providers installed
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
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.
Adds
pytest.importorskipguards to core tests that import optional provider packages so they skip gracefully when providers are not installed. Removes 6 provider packages fromairflow-coredev dependencies. This enablescd airflow-core && uv sync && pytestto work standalone. The pytest.importorskip pattern is already established in the codebase (test_executor_loader.py, test_connection.py). These tests continue to run in CI and in full workspace environments (uv sync --all-packages).The remaining provider-dependent tests all test core functionality (executor loading, serialization, CLI parsing) using provider classes as test inputs. Previous PRs (#48113, #49178, #54635) already moved truly provider-specific tests. These belong in core and are guarded rather than moved.
closes: #60770
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (claude-opus-4-6) following the guidelines