Skip to content

Commit 3d78de2

Browse files
committed
chore: fix lint errors
1 parent 34e08a0 commit 3d78de2

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

tests/e2e/test_local_session.py

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,6 @@
2222
TEST_RANDOM = 23
2323

2424

25-
@pytest.fixture
26-
def auto_deterministic_message_fixtures(deterministic_message_fixtures: None) -> None:
27-
"""Auto-use deterministic message fixtures for all tests in this module."""
28-
pass
29-
30-
3125
@pytest.fixture(name="mock_create_local_connection")
3226
def create_local_connection_fixture(
3327
request_handler: RequestHandler, log: CapturedRequestLog
@@ -74,7 +68,7 @@ def build_raw_response(
7468
connect_nonce: int | None = None,
7569
ack_nonce: int | None = None,
7670
) -> bytes:
77-
"""Build an encoded RPC response message."""
71+
"""Build an encoded response message."""
7872
message = RoborockMessage(
7973
protocol=protocol,
8074
random=23,
@@ -179,7 +173,14 @@ async def test_l01_session(
179173
log: CapturedRequestLog,
180174
snapshot: syrupy.SnapshotAssertion,
181175
) -> None:
182-
"""Test connecting to a device that speaks the L01 protocol.."""
176+
"""Test connecting to a device that speaks the L01 protocol.
177+
178+
Note that this test currently has a delay because the actual local client
179+
will delay before retrying with L01 after a failed 1.0 attempt. This should
180+
also be improved in the actual client itself, but likely requires a closer
181+
look at the actual device response in that scenario or moving to a serial
182+
request/response behavior rather than publish/subscribe.
183+
"""
183184
# Client first attempts 1.0 and we reply with a fake invalid response. The
184185
# response is arbitrary, and this could be improved by capturing a real L01
185186
# device response to a 1.0 message.

0 commit comments

Comments
 (0)