Closed
Bug 835639
Opened 11 years ago
Closed 10 years ago
Tap() wont work in "Test UI > Keyboard Test", but click() works
Categories
(Remote Protocol :: Marionette, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wachen, Unassigned)
References
Details
(Whiteboard: [touch])
This bug is migrate from https://github.com/mozilla/gaia-ui-tests/issues/333 with suggestion of malini. I was writing testing scripts of keyboard in gaia-ui-test. However, I found an interesting issue: STR 1. When you try to automatically testing in "Test UI" app. 2. Enter keyboard tests 3. Switch to keyboard and use the following code. text = self.marionette.find_element('css selector', "input[type='text']") textarea = self.marionette.find_element('css selector', 'textarea') text.click() textarea.click() Click() for input column in view would work. However, self.marionette.tap(text) self.marionette.tap(textarea) Won't work proper. Click() still works, but tap(doesn't work) Suspect there is an issue to tap/focus the elements here. I tried to do some changes. I found that WebElement.focus() kind of works but not the behavior we expect. Please help on investigation if you have a fix or any ideas. I would also try to contribute to this issue and report the most up-to-date status.
Updated•11 years ago
|
Comment 1•11 years ago
|
||
I can't seem to locate the text/textarea fields in the 'UI tests' app after selecting the Keyboard tests, can you repeat the STR and see if they still work for you? If not, can you update the STR?
Updated•10 years ago
|
Whiteboard: [touch]
Updated•10 years ago
|
Keywords: ateam-marionette-goal,
ateam-marionette-userinput
Updated•10 years ago
|
Keywords: ateam-marionette-goal,
ateam-marionette-userinput
Comment 2•10 years ago
|
||
Original test case is gone but I checked tap for all textarea fields on the new version of UI Tests and they all work correctly.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•1 year ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•