Add tests for common compat standard utilities - #72487
Conversation
|
Thanks for the contribution! I think this test should use an independent expected list instead of parametrizing from Right now Could we make the expected public exports explicit in the test, then assert both |
Ensure the compatibility import surface stays covered as supported Airflow versions evolve.
Detect accidental removal of public compatibility exports even when the advertised export list changes with the import map.
04943eb to
9081496
Compare
|
@fat-catTW |
Add coverage for the compatibility imports exposed by
common.compat.standard.utils.The tests verify every name in
__all__resolves through the compatibility import map and that unknown attributes retain the expectedAttributeErrorcontract. This removes the corresponding entry fromOVERLOOKED_TESTS.related: #35442
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines
Drafted-by: Codex (GPT-5); reviewed by @dhkim1920 before posting