Bump pytest-httpx from 0.30.0 to 0.32.0

[dependabot]

Bumps pytest-httpx from 0.30.0 to 0.32.0.

Release notes

Sourced from pytest-httpx's releases.

0.32.0 (2024-09-27)

Added

• The following option is now available:
  • can_send_already_matched_responses (boolean), defaulting to False.
• Assertion failure message in case of unmatched responses is now linking documentation on how to deactivate the check.
• Assertion failure message in case of unmatched requests is now linking documentation on how to deactivate the check.
• httpx.TimeoutException message issued in case of unmatched request is now linking documentation on how to reuse responses (in case some responses are already matched).

Fixed

• Documentation now clearly state the risks associated with changing the default options.
• Assertion failure message in case of unmatched requests at teardown is now describing requests in a more user-friendly way.
• Assertion failure message in case of unmatched requests at teardown is now prefixing requests with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• Assertion failure message in case of unmatched responses at teardown is now prefixing responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now prefixing available responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now listing unmatched responses (in registration order) before already matched one (still in registration order).
  • The incentive behind this change is to help identify a potential mismatch faster as the first unmatched response is the most likely to be the one expected to match.
• Response description in failure messages (httpx.TimeoutException message issued in case of unmatched request or assertion failure message in case of unmatched responses at teardown) is now displaying if the response was already matched or not and less misleading in it's phrasing about what it can match (a single request by default).

Changed

• Last registered matching response will not be reused by default anymore in case all matching responses have already been sent.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(can_send_already_matched_responses=True) option.
  • The incentive behind this change is to spot regression if a request was issued more than the expected number of times.
• HTTPXMock class was only exposed for type hinting purpose. This is now explained in the class docstring.
  • As a result this is the last time a change to __init__ signature will be documented and considered a breaking change.
  • Future changes will not be documented and will be considered as internal refactoring not worth a version bump.
  • __init__ now expects one parameter, the newly introduced (since [0.31.0]) options.
• HTTPXMockOptions class was never intended to be exposed and is now marked as private.

0.31.2 (2024-09-23)

Fixed

• httpx_mock marker can now be defined at different levels for a single test.

0.31.1 (2024-09-22)

Fixed

• It is now possible to match on content provided as async iterable by the client.

0.31.0 (2024-09-20)

Changed

• Tests will now fail at teardown by default if some requests were issued but were not matched.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(assert_all_requests_were_expected=False) option.
• The httpx_mock fixture is now configured using a marker (many thanks to Frazer McLean).

  # Apply marker to whole module
  pytestmark = pytest.mark.httpx_mock(assert_all_responses_were_requested=False)
  Or to specific tests
  @​pytest.mark.httpx_mock(non_mocked_hosts=[...])
  def test_foo(httpx_mock):
  ...

... (truncated)

Changelog

Sourced from pytest-httpx's changelog.

[0.32.0] - 2024-09-27

Added

• The following option is now available:
  • can_send_already_matched_responses (boolean), defaulting to False.
• Assertion failure message in case of unmatched responses is now linking documentation on how to deactivate the check.
• Assertion failure message in case of unmatched requests is now linking documentation on how to deactivate the check.
• httpx.TimeoutException message issued in case of unmatched request is now linking documentation on how to reuse responses (in case some responses are already matched).

Fixed

• Documentation now clearly state the risks associated with changing the default options.
• Assertion failure message in case of unmatched requests at teardown is now describing requests in a more user-friendly way.
• Assertion failure message in case of unmatched requests at teardown is now prefixing requests with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• Assertion failure message in case of unmatched responses at teardown is now prefixing responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now prefixing available responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now listing unmatched responses (in registration order) before already matched one (still in registration order).
  • The incentive behind this change is to help identify a potential mismatch faster as the first unmatched response is the most likely to be the one expected to match.
• Response description in failure messages (httpx.TimeoutException message issued in case of unmatched request or assertion failure message in case of unmatched responses at teardown) is now displaying if the response was already matched or not and less misleading in it's phrasing about what it can match (a single request by default).

Changed

• Last registered matching response will not be reused by default anymore in case all matching responses have already been sent.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(can_send_already_matched_responses=True) option.
  • The incentive behind this change is to spot regression if a request was issued more than the expected number of times.
• HTTPXMock class was only exposed for type hinting purpose. This is now explained in the class docstring.
  • As a result this is the last time a change to __init__ signature will be documented and considered a breaking change.
  • Future changes will not be documented and will be considered as internal refactoring not worth a version bump.
  • __init__ now expects one parameter, the newly introduced (since [0.31.0]) options.
• HTTPXMockOptions class was never intended to be exposed and is now marked as private.

[0.31.2] - 2024-09-23

Fixed

• httpx_mock marker can now be defined at different levels for a single test.

[0.31.1] - 2024-09-22

Fixed

• It is now possible to match on content provided as async iterable by the client.

[0.31.0] - 2024-09-20

Changed

• Tests will now fail at teardown by default if some requests were issued but were not matched.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(assert_all_requests_were_expected=False) option.
  • The incentive behind this change is to spot unexpected requests in case code is swallowing httpx.TimeoutException.
• The httpx_mock fixture is now configured using a marker (many thanks to Frazer McLean).

  # Apply marker to whole module
  pytestmark = pytest.mark.httpx_mock(assert_all_responses_were_requested=False)
  Or to specific tests
  @​pytest.mark.httpx_mock(non_mocked_hosts=[...])
  def test_foo(httpx_mock):
  ...

... (truncated)

Commits

• dcc725f Merge pull request #160 from Colin-b/develop
• 2da1848 Avoid unused variables with a dedicated name
• 50bd257 Document how to use httpx.URL
• 179007e Document the new link
• 9ddead6 Link response reuse documentation
• 08b3803 Release version 0.32.0
• 853c5f7 Keep number of tests up to date
• 33cd894 Merge remote-tracking branch 'origin/develop' into feature/toggle_repeat
• d9a9b86 Cleanup failure description for can_send_already_matched_responses users as well
• 356026b Cleanup failure description
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #1916.