-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run unit tests with airflow installed from packages #39513
Run unit tests with airflow installed from packages #39513
Conversation
1194fde
to
f115589
Compare
As explained in the devlist - This PR - specifically this job https://github.com/apache/airflow/actions/runs/9023444361/job/24795410794?pr=39513 runs Provider unit tests against Airflow 2.9.1 installed from PyPI. I will add a few comments and tag relevant people in the places where I need help to understand if my changes are ok or not as we need to add compatibility layer for our tests to make it works for 2.9.1 (and later we should do the same for 2.8 and 2.7). |
tests/providers/amazon/aws/executors/batch/test_batch_executor.py
Outdated
Show resolved
Hide resolved
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
This is a follow-up on #39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
…he#39513) This PR adds the option of running unit tests for providers against a specific airflow version (for example released version in PyPI) and enables it for back-compatibility testing for 2.9.1. In the future it could be used to run forward-compatibility testing with Airflow 3 as well.
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
This PR adds the option of running unit tests for providers against
a specific airflow version (for example released version in PyPI)
and enables it for back-compatibility testing for 2.9.1. In the
future it could be used to run forward-compatibility testing with
Airflow 3 as well.
^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.