How to Master Mobile Automation in QA

Sergey Komarov

I’m Senior QA Automation engineer at Oxagile

2

Former military radio engineer; Been in IT since 2008; 4 years of manual testing experience; 2 years of Web application

automation experience; Been specializing in mobile

automation testing since 2014.

QA automation works for:

unit testing API testing mobile UI testing (hot topic these

days)

2

cross-platform testing frequent release cycles unattended testing multiple application versions manual testing had to be made fun

again 4

Why our mobile app needed it:

And let’s not forget:

…that’s what the customer wanted, too

3

Enter Appium

5

Devs can make future test automation easier:

6

Android: contentDescription resource id

iOS: name (accessibility id) label value

We made test automation a part of CI:

7

Build job Test job

Mac OS and devices

A lot of things can be tested:

8

any app type (native, hybrid, or web) any user action (dragging, multi-

touch, file upload, etc.) device actions (rotation, locking, etc.)

Feel the power:

8

all capabilities of Android adb JavaScript injections libimobiledevice library

Limited support or not yet possible to:

9

switch between apps emulate external events like sending an SMS monitor hardware parameters like battery charge test audio (except on real devices) test flashing or flickering elements due to Appium

slowness

So where do we go from here?

10

I’m going out for some beer

Seriously though, automation helps with:

11

simulating user actions complex scenarios frequent repetitive tasks long testseliminating the human

factor

A few beautiful charts

11

Smoke test Regression test

Do not overload

11

UI testing has its limits:

API through UImore unit testingsome things are

better left to manual testers

Oxagile Automation Team

Oxagile core clients

Thanks for viewing!Now, please look at the light, forget everything you heard,

and we’ll be the only wonder-working team out there

18