How can automate virtual keyboard using Embedded Wizard testing framework

Question

hi,

I am using Embedded Wizard testing framework. I have to enter data to text editor using Virtual keyboard.

Can u pls help me to resolve this?

Answer 1

Hi SKI,

you can use the method:

SendTouchEvent( point aPos )

from the class Test::Case to emulate touch events on the keyboard.

Best regards,

Julian

 

Comments

Hi jwi,

I tried with SendTouchEvent() by passing position of one key in virtual keyboard. But it doesn't worked.

---

Hi SKI,

there can be multiple reasons why this is not working:

1. Wrong position. Be aware that the origin of the coordinate system is the top-left corner

2. Maybe there is some screen transition ongoing and the keyboard is not yet ready to get key touch events. In this case you need to delay the SendTouchEvent() until it can

I hope this helps you.

Best regards,

Julian

---

AfterCapslockPress

BeforeCapslockPressed

Hi,

The position I tried was correct that I confirmed with developers. I added delay also. But till not worked.

Please find the attached screenshots. First  I clicked In Patient Id textbox, then virtual keyboard is displayed.

Secondly I called SendTouchEvent(point(80,572)); with position of caps lock key. That also worked.

After then I called  SendTouchEvent with position of letter 'a' in virtual keyboard. But that not worked.

I tried with postion of other letters also. But not worked.

Any special handling should be done for letters?

 

 

---

Hi SKI,

ich figured it out, there is an issue when a keyboard button gets feeded with just a single press and release.

I wrote you a PM where you can download the fixed version.

Best regards,

Julian

---

what all modifications have you done to resolve that keyboard press issue?

---

Hi mvg,

I modified the class ExtendedVirtualKeyboard::KeyboardTemplate.

The issue was that inside UpdateViewState() the button view was obtained by FindViewAtPosition(). Because UpdateViewState() gets called asynchronious the pressed button view was not immediately available when it was needed. This was not recognized while manual testing because normal touch sequences are taking much longer. Now the button view is immediately obtained inside the onPress.

To figure out what excatly has changed you could do a split of the unit ExtendedVirtualKeyboard of the first and second draft and compare the KeyboardTemplate.ewui with a diff tool of you choice.

https://doc.embedded-wizard.de/split-attr?v=11.00

Best regards,

Julian

---

Hi,

With the fixed version, the keyboard press issue is resolved.

Thank you

---

Great, thanks for the feedback!