Problem
Four entry-point tests intentionally pass both a deprecated parameter and its replacement to verify the resulting conflict error. The tests assert the ValueError, but they do not capture the expected DeprecationWarning emitted first.
Consequently, a normal suite run reports four warnings and the suite cannot be run with warnings treated as errors, even though these warnings are part of the behavior under test rather than unexamined application output.
Proposed coverage
Wrap the four conflict cases in pytest.warns(DeprecationWarning) while retaining the existing error-message assertions. This documents both parts of the contract and permits warning-strict test execution without changing production behavior.
Problem
Four entry-point tests intentionally pass both a deprecated parameter and its replacement to verify the resulting conflict error. The tests assert the
ValueError, but they do not capture the expectedDeprecationWarningemitted first.Consequently, a normal suite run reports four warnings and the suite cannot be run with warnings treated as errors, even though these warnings are part of the behavior under test rather than unexamined application output.
Proposed coverage
Wrap the four conflict cases in
pytest.warns(DeprecationWarning)while retaining the existing error-message assertions. This documents both parts of the contract and permits warning-strict test execution without changing production behavior.