Skip to content

Capture expected deprecation warnings in entry-point tests#582

Draft
claell wants to merge 1 commit into
sciunto-org:mainfrom
claell:test/capture-expected-deprecation-warnings
Draft

Capture expected deprecation warnings in entry-point tests#582
claell wants to merge 1 commit into
sciunto-org:mainfrom
claell:test/capture-expected-deprecation-warnings

Conversation

@claell

@claell claell commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Capture the expected DeprecationWarning in legacy/new parameter conflict tests.
  • Retain the existing ValueError and message assertions.
  • Make the complete suite pass with warnings treated as errors.

Closes #581.

Validation

  • pytest -p no:cacheprovider -W error: 2,576 passed, 12 skipped.
  • Complete pre-commit hook suite: passed.

Review note

This is a test-only change. It makes warnings already emitted by the intended conflict path explicit rather than suppressing warnings globally.

AI assistance

This pull request was prepared with ChatGPT Codex using GPT-5.6 Sol with high reasoning effort. Codex assisted with warning analysis, branch isolation, and validation. Automated validation is not a substitute for maintainer review.

Keep conflicting legacy-parameter tests explicit without leaking expected warnings into suite output.
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.

Capture expected deprecation warnings in entry-point tests

1 participant