Top Banner
Christian Breitwieser [email protected] Observed Issues When Starting With Mobile Test Automation
9

Observed Issues When Starting With Mobile Test Automation

Apr 16, 2017

Download

Software

Testplus GmbH
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Observed Issues When Starting With Mobile Test Automation

Christian Breitwieser

[email protected]

Observed Issues When Starting WithMobile Test Automation

Page 2: Observed Issues When Starting With Mobile Test Automation

2

Agenda

» Sample Test Case

» Frequent Issues in Mobile Test Automation

» How to Deal with These Issues

Page 3: Observed Issues When Starting With Mobile Test Automation

3

Sample Test Case

Mobile Test Scenario

Create New File Save File Validate And Delete File

Page 4: Observed Issues When Starting With Mobile Test Automation

4

A Look Into Ranorex

http://www.ranorex.com

Page 5: Observed Issues When Starting With Mobile Test Automation

5

Frequent Issues…

» Automating all manual tests

» Prioritize tests

» Automate tests with the highest

risk coverage

» Far too long modules/recordings

» Split recordings

» Create reusable modules

Page 6: Observed Issues When Starting With Mobile Test Automation

6

Frequent Issues…

» Limited experience of testers in the mobile field

» Do not flip the testing pyramid

» Train those in charge of test automation

» Ask for external help

» Lack of cooperation between testers and developers

» Use Ranorex ;-)

functional

integration

unit

Page 7: Observed Issues When Starting With Mobile Test Automation

Mobile test automation is not rocket science…

Page 8: Observed Issues When Starting With Mobile Test Automation

Mobile test automation is not rocket science…

… especially not with

Page 9: Observed Issues When Starting With Mobile Test Automation

Say Hello to Truly Automated Awesomeness!

ranorex.com/why

Christian Breitwieser

[email protected]