gopidesupavan commented on issue #53130: URL: https://github.com/apache/airflow/issues/53130#issuecomment-3062082772
> > Have a docker compose setup that will spin up an actual airflow api server and workers > > This is already happening in docker-compose tests. We actually use our docker-compose quick start to run airflow and run some API calls to test it. > > > Install task sdk in a venv and use it's client to interact with the airflow api server > > Yep. We have similar test for Python API - we start the api-server there and let Python API test script to run it. It could be done very similarly > > > We will be testing interfaces here without writing dags / tests > > Yep. I think also what we could do is to have a different mode for existing tests. I assume most of our tests for task-sdk are using some kind of mocking, but possibly we could add a way to run the same tests but do not use mocking, but a real api-server instance. This way we could reuse the existing tests - they would be a bit more complicated but if we do it right, we could avoid duplicate work on writing similar tests for unit and "integration" testing. Yeah with different modes option is good idea, run with actual environment or mock environment. I have a long plan to get it things workout with test-containers for end to end or config driven test environment, I will see if possible i will try to bring this up in next week. @amoghrajesh let me know if any effort required i can join with you and workout. -- 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]
