search

sangmingming / robotium

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

unclickable buttons disrupt test #70

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Create dialog(DIALOG1) with button with text "ok".
2.out of this dialog open another one(DIALOG2) with another button and text "ok"
3.perform solo.clickOnButton("ok")

What is the expected output? What do you see instead?
I would expect the button in DIALOG2 to receive click .
I see no click at all-

What version of the product are you using? On what operating system?
Version 2.1.1 windows xp

Please provide any additional information below.
By debugging i see that the button which is found is the button on 
DIALOG1(which is hidden behind).
then the click initiate launches with xY coordinates which match the hidden 
"ok".

The same happens when i try solo.clickonindex(0).
I guess the indexes numbered are messed too because of the hidden DIALOG1.

Original issue reported on code.google.com by yair.oha...@gmail.com on 14 Feb 2011 at 9:44

GoogleCodeExporter commented 9 years ago 
Thanks for this. What happens if you use: clickOnText("Ok", 2)?

Original comment by renasr...@gmail.com on 15 Feb 2011 at 5:02

GoogleCodeExporter commented 9 years ago

Original comment by renasr...@gmail.com on 15 Feb 2011 at 5:39

GoogleCodeExporter commented 9 years ago 
Please try the attached jar. Hopefully all your problems are solved now.

Original comment by renasr...@gmail.com on 15 Feb 2011 at 3:35

Attachments:

GoogleCodeExporter commented 9 years ago 
Great - it does solve my problem thank you.
By the way - i noticed indexes were changed between 2.1 release (were 
incremented by one) and the snapshot( down by one).

IE
solo.clickonbutton(0) -->ver 1.7
solo.clickonbutton(1) -->ver 2.1
solo.clickonbutton(0) -->ver 2.1.1-SNAPSHOT
all those produce same click...

Is it going to stay like that - people are probably adjusting their code and it 
should be persistent ( I think index 0 is the right way to go...)

Original comment by yair.oha...@gmail.com on 15 Feb 2011 at 8:24

GoogleCodeExporter commented 9 years ago 
Great that it is working well for you. It should definitely be 0. The version 
that you have tried will be the one that is released as long as all the testing 
goes well.

Original comment by renasr...@gmail.com on 15 Feb 2011 at 8:35

GoogleCodeExporter commented 9 years ago 
This issue has been fixed in Robotium 2.2.

Original comment by renasr...@gmail.com on 21 Feb 2011 at 6:00