potiuk commented on PR #21323: URL: https://github.com/apache/airflow/pull/21323#issuecomment-1091451291
> But isn't that always the assumption when we mock external dependencies – that we're doing it correctly. There is always that risk that the assumptions are wrong. But that would the hopefully be discovered during alpha/beta testing. Not really. We rathe follow the typical test pyramid: This is just one incarnation of it: https://martinfowler.com/articles/practical-test-pyramid.html * Plenty uf real unit tests * Far less number of integration tests with actual local services including actual Docker and actual Kubernets tests - KiND based (those are special cases of Integration tests) * Very few system tests (AIP-4 an AIP-47 are about fully automating those) talking to actual external services. This is rather comprehensively described in https://github.com/apache/airflow/blob/main/TESTING.rst (all the test types we have are described there). I personally think the "test pyramid" approach is far more useful than "only unit tests". I find the latter a bit too dogmatic and I think our integration tests and system tests play a role there (System tests especially for Providers in the future). -- 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]
