austgl / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

Cannot click on Nexus One #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Added 
    <uses-sdk android:minSdkVersion="4" />
    <supports-screens android:anyDensity="true"/>  to my AndroidManifest.xml as suggested in a click problem. 
2. solo.waitForActivity("MyActivity", 20000);
   solo.assertCurrentActivity("", MyActivity.class);
   solo.sleep(100);
   solo.clickOnMenuItem("Menu item", false);
3. Application loads, MyActivity launches, menu opens and "Menu item" appears.

What is the expected output? What do you see instead?
Actual result: Menu item is being selected but not clicked
Expected result: Menu item should be clicked and a new activity will be launched

What version of the product are you using? On what operating system?
Testing 1.9.0 on Nexus One running Froyo (2.2.1)

Please provide any additional information below.
None of the click methods are working and they dont throw an exception.

I'm attaching you the screen shot that illustrates the selected but not clicked 
menu button.

Original issue reported on code.google.com by burcujdogan on 3 Dec 2010 at 7:40

Attachments:

GoogleCodeExporter commented 9 years ago
Does it work on the emulator?

Original comment by renasr...@gmail.com on 3 Dec 2010 at 9:27

GoogleCodeExporter commented 9 years ago
Yes, it works - tested on emulator 1.6 and 2.1

Original comment by burcujdogan on 4 Dec 2010 at 10:25

GoogleCodeExporter commented 9 years ago
Does it work if you use Touchutils instead for clicking the menu item?

Original comment by renasr...@gmail.com on 5 Dec 2010 at 7:28

GoogleCodeExporter commented 9 years ago
I've tried this with TouchUtils and it doesn't work.  There is outstanding 
defect with Google about this.  
http://code.google.com/p/android/issues/detail?id=6564

Original comment by lim....@gmail.com on 6 Dec 2010 at 11:20

GoogleCodeExporter commented 9 years ago
The problem lies with Google.

Original comment by renasr...@gmail.com on 7 Dec 2010 at 3:06