Hi,
I am running an Android instrumentation test project in Jenkins based on
Maven using android SDK 4.0.3 API level 15. The emulator is running with
the -no-window option. I am using the option to run an emulator with
properties, not a pre-existing emulator. Emulator snapshot reuse and
hw.audioInput are off.
The logcat shows that the application starts and the test is executed
within the Dalvik VM. However, it seems the test cannot interact with the
UI. My robotium test clicks on a button and waits for a text to appear, but
the button is not found:
[INFO] localhost_59383_unknown_sdk: junit.framework.AssertionFailedError:
Button with text: 'Login' is not found!
The symptom is the same as with an emulator in my local build which has its
screenguard on.
Normally, the Android Emulator plugin should unlock the screen
automatically. Is that correct or is there an option which must be set in
order to enable automatic unlocking of the screen?
How can I analyze if the emulator was successfully unlocked in a headless
Jenkins? Is there a log I can enable?
Best regards,
Dietrich
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
