mobile automation

5/28/2018 MOBILE AUTOMATION

1/10

MOBILE

APPLICATION

AUTOMATION

TOOLS

SUBHAN ABDUL


2/10

Need for Mobile Automation New version of OS / Devices / Application

Functional Test case : 800 : 6 Man days : Single Device

Regression Test cases: 350 : 3 Man days : Single Device


3/10

APPROACH

Open Source vs.

Enterprise

Demo Evaluation Final


4/10

OPEN SOURCE

SL

NO

TOOL IOS ANDRIOD

1 MONKEY TALK

2 APPIUM

3 SIKULI

4 NATIVE DRIVER : GOOGLE

6 ROBOTINUM

7 CUCUMBER WEB DRIVER

8 MONKEY RUNNER

9 FRANK

10 ZUCHINI

11 UI AUTOMATOR- ANDROID


5/10

ENTERPRISESL # TOOL IOS ANDRIOD BLACK

BERRY

WINDOWS

1 TEST PLANT

2 RANOREX

3 SEE TEST

4 SILK MOBILE

5 DEVICE ANY

WHERE

6 SQUISH

7 MTAS


6/10

ENTERPRISE

SL

#

TOOL IOS ANDRIOD BLACK

BERRY

WINDOWS

8 M-eUX TEST

9 RATIONAL(RTW)

10 SOASTA TOUCHTEST

11 TELERIK

12 PERFECTO MOBILE

13 ZAP FIX

14 TPLAN ROBOT


7/10

DEMO FROM VENDORAssessmentCriteria

Smartphone/Tablet device OS version supported

Can the tool run the tests on the device simulators?

Can the tool run the tests on the Smartphone?

Can the tool run the tests on the tablet?

What kind of validation can the tool perform?

What kind of datacan be retrieved from the controls for

validation?

Does creatinganew build affect existingscripts (Broken links to

controls, etc...)? Which then require rework of existing scripts.

This might need to be verified usingTELUS app.

Does different resolutions on the devices aff ect if the scripts

run ornot. In otherwords, can a script created usingone device

be usable on different devices with different screen

resolutions?


8/10

TOOL EVALUATION CHECK LIST


9/10

TOOL EVALUATION

IDENTIFICATION

STABILITY

PERFORMANCE

NON INSTRUMENTEDAPPLICATIONS

PARAMETERS

TEST MANAGEMENT-

QUALIY CENTER

SCRIPTING

42 13

COST 2 4 31


10/10

THANK YOU

mobile automation

Documents