Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

How to Master Mobile Automation in QA

•Download as PPTX, PDF•
•
Oxagile
Oxagile

The document discusses how to master mobile automation testing in QA. It provides an overview of mobile automation testing, including why it is useful for frequent releases, unattended testing, and testing multiple app versions. It also discusses the benefits of using Appium for cross-platform mobile testing on Android and iOS. Key steps discussed include integrating mobile test automation into a CI pipeline and the types of tests that can be automated, like user actions, device actions, and app functionality. Limitations of mobile test automation are also addressed.

Related slideshows

Continuous testing on emulators using the espresso test automation framework
Continuous testing on emulators using the espresso test automation frameworkContinuous testing on emulators using the espresso test automation framework
Continuous testing on emulators using the espresso test automation framework
 
Boston meetup blaze_meter_feb2017
Boston meetup blaze_meter_feb2017Boston meetup blaze_meter_feb2017
Boston meetup blaze_meter_feb2017
 
Robot test system for Car navigation and Automotive
Robot test system for Car navigation and AutomotiveRobot test system for Car navigation and Automotive
Robot test system for Car navigation and Automotive
 
1 of 16
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? 1 I’m going out for some beer 
Seriously though, automation helps with: 1  simulating user actions  complex scenarios  frequent repetitive tasks  long tests  eliminating human errors
A few beautiful charts 1 Smoke test Regression test
Do not overload  1 UI testing has its limits: API through UI more unit testing some 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  1

More Related Content

How to Master Mobile Automation in QA

  • 1. How to Master Mobile Automation in QA
  • 2. 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.
  • 3. QA automation works for:  unit testing  API testing  mobile UI testing (hot topic these days) 2
  • 4.  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:
  • 5. And let’s not forget: …that’s what the customer wanted, too  3
  • 7. Devs can make future test automation easier: 6 Android:  contentDescription  resource id iOS:  name (accessibility id)  label  value
  • 8. We made test automation a part of CI: 7 Build job Test job Mac OS and devices
  • 9. 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.)
  • 10. Feel the power: 8  all capabilities of Android adb  JavaScript injections  libimobiledevice library
  • 11. 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
  • 12. So where do we go from here? 1 I’m going out for some beer 
  • 13. Seriously though, automation helps with: 1  simulating user actions  complex scenarios  frequent repetitive tasks  long tests  eliminating human errors
  • 14. A few beautiful charts 1 Smoke test Regression test
  • 15. Do not overload  1 UI testing has its limits: API through UI more unit testing some things are better left to manual testers
  • 16. 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  1