Adaverse opened a new issue, #31809:
URL: https://github.com/apache/airflow/issues/31809
### Apache Airflow version
2.6.1
### What happened
I was going through
`tests/system/providers/microsoft/azure/example_azure_blob_to_gcs.py`, and
after grasping the motive behind the system test, one thing is that each of
these tests should be self-sufficient dags and should act as a good example for
that specific object (sensor, operator, etc...) under test. In the above case,
the dag flow -
```
(
wait_for_blob
>> wait_for_blob_async
>> wait_for_blob_prefix
>> wait_for_blob_prefix_async
>> transfer_files_to_gcs
)
```
Please correct me if I'm wrong, but isn't this test waiting for a blob to
exist before testing the main operator (that it is supposed to test) i.e.
`AzureBlobStorageToGCSOperator`. Hence waiting for some external service (or
some dag or task) to create the blob to continue with the test. Or am I missing
something here?
According to me, it should have been something like this -
```
create_blob_azure
>> transfer_files_to_gcs
>> check_in_gcs # for successful transfer
```
### What you think should happen instead
_No response_
### How to reproduce
.
### Operating System
.
### Versions of Apache Airflow Providers
.
### Deployment
Other
### Deployment details
_No response_
### Anything else
_No response_
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
