gopidesupavan commented on code in PR #56124: URL: https://github.com/apache/airflow/pull/56124#discussion_r2442170000
########## dev/breeze/doc/05_test_commands.rst: ########## @@ -197,6 +197,25 @@ Here is the detailed set of options for the ``breeze testing airflow-ctl-tests`` :width: 100% :alt: Breeze testing airflow-ctl-tests +Running airflowctl integration tests +.................................. + +You can use Breeze to run the airflowctl integration tests. Those tests are run using Production image by default +and the tests are running with the docker-compose we have for airflowctl tests. + +.. image:: ./images/output_testing_airflow-ctl-integration-tests.svg + :target: https://raw.githubusercontent.com/apache/airflow/main/dev/breeze/images/output_testing_airflow-ctl-integration-tests.svg + :width: 100% + :alt: Breeze testing airflow-ctl-integration-tests + +You can also iterate over those tests with pytest command but unlike regular unit tests, they need to be run in +a local venv. You can build the prod image with breeze and that will be used by default if present to run the tests. + +You can override the ``DOCKER_IMAGE`` environment variable to point to the image to test using the +``breeze testing task-sdk-integration-tests`` command. Review Comment: this should be ctl ########## dev/breeze/doc/05_test_commands.rst: ########## @@ -197,6 +197,25 @@ Here is the detailed set of options for the ``breeze testing airflow-ctl-tests`` :width: 100% :alt: Breeze testing airflow-ctl-tests +Running airflowctl integration tests +.................................. + +You can use Breeze to run the airflowctl integration tests. Those tests are run using Production image by default +and the tests are running with the docker-compose we have for airflowctl tests. + +.. image:: ./images/output_testing_airflow-ctl-integration-tests.svg + :target: https://raw.githubusercontent.com/apache/airflow/main/dev/breeze/images/output_testing_airflow-ctl-integration-tests.svg + :width: 100% + :alt: Breeze testing airflow-ctl-integration-tests + +You can also iterate over those tests with pytest command but unlike regular unit tests, they need to be run in +a local venv. You can build the prod image with breeze and that will be used by default if present to run the tests. + +You can override the ``DOCKER_IMAGE`` environment variable to point to the image to test using the +``breeze testing task-sdk-integration-tests`` command. + +The task-sdk tests are in ``task-sdk-tests/`` folder in the main repo. Review Comment: same here -- 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]
