Test Automation of Android, iphone
and ipad Apps with Zap – Fix, Keyword View and The Expert View
Automation Back Ground → As
there are multiple aspect of the application life cycle that stay
constant regardless of the platforms, whether it be mainframe batch,
online, Client server, mobile and web. There are some deep difference
specifically connected to the application of mobile.
First is related to user interfaces.
It's no longer a GUI, It is the NUI – Natural User Interface;
finger base input, This contains multi-touch gesture on the virtual
keyboard and the even extend to the voice command.
There are also some points that are
cool for the NUI, containing new way of trigger the application
event, Like swipe / flick to scrolls and pans, Pinches / Stretches to
Zoom, Tap to click, even Shake to do whatever make sense to the apps.
But everything come with the price and
there are few thing that are not so cool with the NUI. Small screen
make typing the burden some whether the keyboard is the virtual or
not. Soft keyboard often cover the widget and the control in the way
that limit normal interactions. Navigation is the challenged by the
small pieces of the information always around our finger tip.
Then there is the environments. True
multitasking is also limited. The Operating System can break or kill
the background application at any of time. So Mobiles app is more
prone to interruption such as incoming call, or switching to another
application.
Mandatory Part Which should be AWAREyou about the → TOP 7 QUALITY ISSUES WITH THE MOBILE
ENABLING OR ACTIVATING TESTAUTOMATION FOR MOBILE → FIRST CLICK HERE AND BECOME AWARE ABOUT IT
Keyword View and The Expert View:
Same just as we use the QTP now a days,
we can toggle bak and forth between the keyword Views and Expert
Views:
 |
| Keyword View and The Expert View |
Data Driven Test:
The Data
table in the QTP is the completely present with the ZPX and the
operate exactly in the same way.
 |
| Data Driven Test |
Object Repository:
Once the object is
gathered, these are completely present in the object repository for
the manipulation and the analysis.
 |
| Object Repository |
Test Results:
Test Result is
given according same way as quite QTP does today. Notice here the
familiar purple rectangle highlighting the controls on focuses in the
steps of test.
 |
| Automation Test Results |
Point to be
noted: ZPX is not just for the Automation of Software / Mobile
Testing → As the uniqueness of ZPX viewer not only shows the
devices, it also allow the interaction. Thus ZPX is the noble
platform for the simplifying the manual testing. Described below is
one example related to ZPX being used with the Sprinter QC. This
example shows, You are leveraging the mirror testing feature of
sprinter to simultaneously tests several instance of AUT, even on the
heterogeneous platform. From this example.: The tests are being
driven on the iPhone but these were automatically switches on the
Android
No comments:
Post a Comment