potiuk commented on code in PR #53332: URL: https://github.com/apache/airflow/pull/53332#discussion_r2220498150
########## dev/breeze/doc/05_test_commands.rst: ########## @@ -317,6 +317,24 @@ through ``breeze testing docker-compose-tests`` command. The docker-compose tests are in ``docker-tests/`` folder in the main repo. +Running task-sdk integration tests +.................................. + +You can use Breeze to run the task-sdk integration tests. Those tests are run using Production image +and they are running test with the Quick-start docker compose we have. Some scenarios of task-sdk tests are run here. + +.. image:: ./images/output_testing_docker-compose-tests.svg + :target: https://raw.githubusercontent.com/apache/airflow/main/dev/breeze/images/output_testing_task-sdk-integration-tests.svg + :width: 100% + :alt: Breeze testing task-sdk-integration-tests + +You can also iterate over those tests with pytest command, but - unlike regular unit tests and +Helm tests, they need to be run in local virtual environment. They also require to have +``DOCKER_IMAGE`` environment variable set, pointing to the image to test if you do not run them +through ``breeze testing task-sdk-integration-tests`` command. Review Comment: That's not entirely right. From what I see you can do: ``` breeze prod-image build ``` And then the local prod image `ghcr.io/apache/airflow/main/prod/python....` (likely it shoudl be updated also above). -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
