TA: Mobile browser - It's all about the touch(start/end)

As we all know, non-touch devices like a desktops have slightly different input from touch devices like mobile. This also means developers do have the option to build a website that does expect touch input instead of a mouse click. If your test suite does do a `element.click` when touch is expected, the click does not fail (at least not currently), so no error is thrown/shown but your script will fail. In one of my previous blog posts I mentioned a solution with execute_script and touchend. I did find out (with the help of the watir community on Slack), this can be resolved easier with Selenium and touch action (only supported on Chrome at the moment of writing).

The specs

In general spec documents are a bit difficult to interpret because of the lack of a clear example, but it gets easier to understand the structure over time. If you look at the specs of selenium-webdriver you get an overview of all possibilities. There are a couple of points you could look if you think about tapping on the screen. On the Watir Slack channel I mentioned `HasTouchScreen` which just refers to `touch`, Lucas T. mentioned `touch` actions and `touch.single_tap` (thanks for helping me out Lucas). So in the specs I found related to touch are these two `TouchActionBuilder` (inherits Actionbuilder) & `TouchScreen` (inherits Object). And as we can see `single_tap` is mentioned on those pages. We just need a Selenium driver and object to execute it since this is not anywhere mentioned in the Watir specs.

Watir to Selenium conversion

I'm using the Lapis_lazuli + Watir combi, so I use `browser` instead of `driver` and also the elements I find are Watir objects instead of Selenium objects. And since Watir is like an extension of Selenium, it's really easy to find the element with LL/Watir and let Selenium take over for some touch action.
As for the `touch` action with Selenium driver you can do `driver = browser.driver` and than `driver.touch...` or just `browser.wd.touch...`.
As for the object you can do `s_elm = elm.wd` to convert a Watir object into a Selenium object.
Now you can perform a touch event on an element like `browser.wd.touch.single_tap(s_elm).perform`.

Tapping the wrong element

For some reason (I still need to figure out why exactly) in my case the element I needed to tap on did not happen, instead it tapped one element (most likely one pixel) to high. I assumed that just like with a `elm.click` (as Justin Ko mentioned on a StackOverflow post) the webdriver will tab in the middle of the element (as also mentioned in the new W3C specs), but that's not the case and it taps in the top left corner of the element and therefore (by overlap or bug) per accident tapped on one element to high. So I ended up with a slightly different solution `touch.down(x,y)` and `touch.up(x,y)`. The final solution looked like this `browser.wd.touch.down(item.centre).up(item.centre).perform`.

Comments

Post a Comment

Popular posts from this blog

PowerShell - How to overcome Azure VM's fixed resolution limitation

Image
Intro This is the first in a series of PowerShell blogposts. I don't know a lot of PowerShell so I'm going to cover this part very short. What is PowerShell? PowerShell is a very powerful framework you can use to automate tasks. For more info, use Google or check the Wiki:  https://en.wikipedia.org/wiki/PowerShell For my current project we use Azure VM's that we use as selenium-grid (hub and nodes). And Visual Studio Online for kicking off builds. So I started to use a fair share of PowerShell in my test automation process. During the setup I came accross a couple of problems that I want to share with you all which I'll spread across a couple of posts. And we start with Azure VM's that have a fixed resolution of 1024 x 768 and how to overcome this issue/limitation. Azure VM's resolution limitation  Let's start with the problem we faced. Our website under test, requires the test machine to have at least a certain resolution ( Which is > 1024 ...
Read more

TA Basics: Website Test Automation on mobile devices via Appium server

Image
Recently I have been focussing on test automation with mobile devices. Specifically Android and iOS (no Windows phone because that platform is as good as dead at the moment). I first wanted to make a complete manual from setting up software and devices/simulators up to a small test script. But due to lack of time I'll focus on specific parts. If you have any questions reguarding the setup, feel free to contact me. So all that said, let's get to the point. The internet is full of blogposts, video's and examples of people testing mobile apps. However I don't test an app, I want to do some web test automation on mobile devices. It took me quiet some time to figure out what exactly I had to use to get it all to work as needed for my project. Setup Mac mini running OSX 10.13.4 High Sierra (Mac machine is needed for iOS simulation) Ruby version 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17] Appium desktop version 1.4.1 (with Appium server 1.7.2) lapis_laz...
Read more

TA: Who doesn't like proxies? Me!

Image
Are you on a company network that is using a proxy to connect to the internet? And do you want (or are you planning) to connect your tests to an external selenium-grid. Than stay tuned, before you get lost in a bunch of answers on the internet that don't resolve the issue you're facing. Source:  https://nl.wikipedia.org/wiki/Proxyserver I'm on a new project and looking into Robotframework. But then I bumped into an issue with the POC I had to make which might result in me convincing the company to switch to Ruby. Anyway long story short. They use a proxy and although the internet has all the answers, you do need to know what specific question to ask to get the correct result. And since proxies are not used that much anymore, it's hard to find the skilled people to help you out and push you in the right direction for a solution. The setup To access the internet, I need a configuration on my computer that will tell Windows to connect to a proxy server. I...
Read more