kaxil commented on issue #53130: URL: https://github.com/apache/airflow/issues/53130#issuecomment-3058863240
Yeah we could partially do that but the reason for other suggestions in https://github.com/apache/airflow/issues/53130#issuecomment-3057560558 is to allow ad-hoc feature testing without running the entire dag and too complex of a dag: example to a) verify what happens end-to-end after heartbeat fails b) verifying previous dag runs c) testing all combinations of XCom. e.g we have 254 combinations in a specific test (that's a defensive test -- but tests like that where we can just parameterize) Separate integration sits somewhere between Unit tests and our system tests. We don't need to test the entire system but the interaction of Task SDK Execution code with the API server -- no need to test different executors. Instead the matrix would be latest API-server with new & last released Task SDK (which will be critical for back-compat from 3.1) These tests should be relatively very quick and allow better debugging (breakpoints). -- 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]
