Skip to content

Clarify testing standard related to caplog assertions in AGENTS.md - #69803

Merged
amoghrajesh merged 2 commits into
apache:mainfrom
amoghrajesh:clarify-caplog-testing-standard
Jul 13, 2026
Merged

Clarify testing standard related to caplog assertions in AGENTS.md#69803
amoghrajesh merged 2 commits into
apache:mainfrom
amoghrajesh:clarify-caplog-testing-standard

Conversation

@amoghrajesh

Copy link
Copy Markdown
Contributor

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Related to #65421

On further investigation, I saw that the blanket "don't use caplog" rule predates the structlog migration.
caplog now resolves to cap_structlog under structlog, which supports safe structured assertions and only raw text matching is fragile and worth discouraging


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@amoghrajesh
amoghrajesh merged commit fd42d86 into apache:main Jul 13, 2026
64 checks passed
joshuabvarghese pushed a commit to joshuabvarghese/airflow that referenced this pull request Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants