tests: fix expected responses after ensure_unlocked() modification
What the developer wrote
Authored by matejcik
tests: fix expected responses after ensure_unlocked() modification
What changed, and why it matters
This is a one-line update to a test file. It changes what the test expects the device to return after a screen unlock step, from a PublicKey message to a Success message. There is no change to the actual device firmware or any security-sensitive behavior.
No security action needed; this is a test-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies tests/device_tests/test_sdcard.py, replacing an expected PublicKey response with Success in the expected-responses list for the SD-card protection lock test. This is purely a test expectation adjustment following a prior change to ensure_unlocked().
Changed components
tests/device_tests/test_sdcard.pyInspect captured patch +1 / −1
diff --git a/tests/device_tests/test_sdcard.py b/tests/device_tests/test_sdcard.py
index 84caf0ce..34409efc 100644
--- a/tests/device_tests/test_sdcard.py
+++ b/tests/device_tests/test_sdcard.py
@@ -246,7 +246,7 @@ def test_sd_protect_lock(session: Session, lock_func: "t.Callable[[Session], Non
client.set_expected_responses(
[
messages.ButtonRequest(code=B.PinEntry),
- messages.PublicKey,
+ messages.Success,
messages.Features,
]
)
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.