tatiana commented on issue #51644: URL: https://github.com/apache/airflow/issues/51644#issuecomment-2969588877
@uranusjr thank you very much for investigating this! > Or do we just ignore all the assets when using test (and not emit an event at all—which might make sense instead since you probably wouldn’t expect a downstream to be triggered when testing a dag) From my perspective, users should have the option to decide whether they want to enable side effects or not when running `airflow dags test`. If we could have a flag, it would be awesome. I am personally interested in both testing asset events using dags test, both from an integration test to be run in the CI, but also being able to view the results in the AF UI later. At the moment, there isn't a good way to verify if assets were emitted as expected in operators that generate asset events dynamically. We also cannot validate listeners' behaviour when using `dag.test` - something that is quite important for people building Airflow integrations and providers. -- 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]
