Issue
Our team recently setup Genymotion for a Jenkins instance using the instructions here. Everything is working awesome except for functional tests, which use Robotium.
It seems that the instrumentation can't figure out how to unlock the device, which means that it is unable to find the necessary UI elements for our functional tests, causing them all to fail.
I've tried taking a snapshot of an unlocked device, restoring that snapshot, and then launching the emulator with Genymotion. However, when I do that, Genymotion gives me an error on start saying that the device is in an incompatible state and then the Jenkins run fails.
So, I'm wondering is there any way to either programatically unlock the screen or launch a Genymotion emulator such that the screen is already unlocked?
EDIT: The tests are targeting API level 10 phones.
Solution
I discovered the solution was to add this line to our Jenkins pre-execute script.
adb shell input keyevent 82
This simulates a press of the menu key, which removes the lock screen.
Answered By - Jonathan
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.