potiuk edited a comment on issue #7389: [AIRFLOW-6763] Make systems tests ready for backport tests URL: https://github.com/apache/airflow/pull/7389#issuecomment-585195708 Hello @ashb @mik-laj @nuclearpinguin @kaxil @dimberman -> I updated the implementation now and it works really nicely. Breeze is now turned into "airflow_1.10.*" testing playground. It will be super-useful to automatically run system tests (currently only for google/* operators) using the latests tests and "example_dags" from "providers", but using the installed airflow version. You can run `./breeze --install-airflow-version <VERSION>` . If you run it with "current" version it works as previously (current version from sources). If you run it with '1.10.1' -> '1.10.9' it will remove the current sources, will uninstall installed airflow master and will install the released version from PIP. The automated installation works out of the box for all versions: 1.10.1 -> 1.10.9. There is an easy way to test installation and run system tests of the released "backported" providers package. If you have binary wheel "providers" package prepared locally or downloaded, you just need to copy the wheel package to "files" dir. Then inside the container with installed airflow version you should be able to run: `pip install /files/<NAME_OF_THE_FILE>.whl` to install the "providers" package. And then the example tests should run out of the box for most operators. The "/opt/airflow/tests" folders and "/providers" folders are mapped into the container (and system test class handles it properly) so that we can still modify the tests locally and run them with airflow 1.10.*. For example, right after installing the 'providers' package you should be able to run: `pytest tests/providers/google/cloud/operators/test_functions_system.py --systems google.cloud` and the system tests It will work for both - 2.0 and 1.10.* series providing that you have proper GCP credentials in "files/airflow-breeze-config/variables.env"
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
