[Dor-bl]

Added unit test coverage for \HardwareActions.unlock\ across both Android and iOS drivers when \mobile: isLocked\ returns \True\ vs \False.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[Copilot]

Copilot review overview

🔵 Needs a closer look

The early-return behavior is not fully asserted in the two affected tests.

Review effort: Lite
Findings: None

What changed in this PR

Adds Android and iOS unit tests for HardwareActions.unlock.

Changes:

• Covers locked and already-unlocked states.
• Verifies expected unlock behavior and early-return paths.

File	Summary
test/​unit/​webdriver/​device/​lock_test.py	Adds Android and iOS unlock branch tests. Two moderate findings note that unlocked cases do not assert mobile: unlock was not sent.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.