Skip to content

Commit 0f42dd6

Browse files
authored
Merge pull request #1212 from Kriechi/fix-467
use Settings equality in tests
2 parents 7be1f28 + 3f72093 commit 0f42dd6

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

test/test_h2_upgrade.py

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ def test_client_settings_are_applied(self, frame_factory):
278278
# start of the connection, do not agree on their initial settings
279279
# state.
280280
assert (
281-
client.local_settings._settings != server.remote_settings._settings
281+
client.local_settings != server.remote_settings
282282
)
283283

284284
# Get the client header data and pass it to the server.
@@ -297,10 +297,6 @@ def test_client_settings_are_applied(self, frame_factory):
297297
)
298298
assert server.data_to_send() == expected_frame.serialize()
299299

300-
# We violate abstraction layers here, but I don't think defining __eq__
301-
# for this is worth it. In this case, both the client and server should
302-
# agree that these settings have been ACK'd, so their underlying
303-
# dictionaries should be identical.
304300
assert (
305-
client.local_settings._settings == server.remote_settings._settings
301+
client.local_settings == server.remote_settings
306302
)

0 commit comments

Comments
 (0)