\n11. Automation Testing IOS Apps using Monkey Talk

\n11.1 MonkeyTalk Introduction

\n11.2 MonkeyTalk IDE

",{"_296":297,"_38":39,"_42":-5,"_40":41,"_60":61,"_298":299,"_353":294},"previewContent","

\n \n
- \n 0.1 Practical approach to mobile application testing Book v0.1\n
\n
\n 1. 1 Mobile App Eco System\n
- \n 1.1 1.1 Understanding Smartphone OS\n
- \n 1.2 1.2 IOS - introduction\n
- \n 1.3 1.3 Android - Introduction\n
- \n 1.4 1.4 Mobile Applications - Introduction\n
- \n 1.5 1.5 Mobile App and their Lifecycle\n
- \n 1.6 1.5.4 Development and Testing Constraint\n
- \n 1.7 1.6 Different Types of Mobile Applications.\n
- \n 1.8 1.6.1 Native Mobile Applications\n
- \n 1.9 1.6.2 Mobile Web Applications _\n
- \n 1.10 _1.6.3 Hybrid Mobile Applications _\n
\n
\n 2. Mobile App Eco System\n
- \n 2.1 Understanding SmartPhone OS\n
- \n 2.2 IOS - introduction\n
- \n 2.3 Android - Introduction\n
- \n 2.4 Mobile Applications - Introduction\n
- \n 2.5 Mobile App and their Lifecycle\n
- \n 2.6 Different Types of Mobile Applications.\n
\n
\n 3. Mobile App Testing Primer\n
\n 4. User Experience Testing Mobile App\n
\n 5. Automation Testing tool primer\n
\n 6. Distributing Mobile Apps\n
\n 7. IOS App Testing Deep Dive\n
\n 8. IOS Application Testing using Simulator\n
\n 9. Automation Testing IOS Apps using Instruments\n
\n 10. Instruments Basics:\n
\n 11. Automation Testing IOS Apps using Monkey Talk\n
- \n 11.1 MonkeyTalk Introduction\n
- \n 11.2 MonkeyTalk IDE\n
\n
\n 12. Performance Testing IOS Apps\n
\n 13. Android App Testing Deep Dive\n
\n 14. Android App Testing using Emulator\n
\n 15. Automation Testing Android apps using Robotium\n
\n 16. Automation Testing Android apps using Monkey Talk\n
\n 17. Performance Testing Android Apps’\n
\n 18. Security Testing Mobile Apps a Primer\n
\n 19. IOS Apps Security Testing\n
\n 20. Android Apps Security Testing\n
\n 21. Cloud Based Automation Testing\n
\n 22. Mobile Web App testing\n
\n 23. Converted Files\n
- \n 23.1 Practical approach to mobile application testing Book v0.1\n
\n
\n 24. 1 Mobile App Eco System\n
- \n 24.1 1.1 Understanding Smartphone OS\n
- \n 24.2 1.2 IOS - introduction\n
- \n 24.3 1.3 Android - Introduction\n
- \n 24.4 1.4 Mobile Applications - Introduction\n
- \n 24.5 1.5 Mobile App and their Lifecycle\n
- \n 24.6 1.5.4 Development and Testing Constraint\n
- \n 24.7 1.6 Different Types of Mobile Applications.\n
- \n 24.8 1.6.1 Native Mobile Applications\n
- \n 24.9 1.6.2 Mobile Web Applications _\n
- \n 24.10 _1.6.3 Hybrid Mobile Applications _\n
\n

\n0.1 Practical approach to mobile application testing Book v0.1

\n\n

Om namo Narayana.

\n\n

Table of content:

\n\n

Mobile App Eco system
Mobile App Testing Primer
Mobile Testing Strategy
Testing Native Android Application Basics.
Testing Native IOS Application Basics
Automation Testing Tools Primer
IOS Native Application Testing √ê Deep Dive
Automation Testing IOS Application using Instruments
IOS Application Performance Testing

\n\n

10.IOS Application security Testing

\n\n

11.Android Native Application Testing √ê Deep Dive

\n\n

12.Android Automation Testing using Robotium

\n\n

13.Android Performance Testing

\n\n

14.Android Security Testing

\n\n

15.IOS and Android Automation Testing using Appium

\n\n

16.Mobile Web Application Testing

\n\n

17.Cloud Based Automation Testing Tools introduction

\n\n

18.Recent advancement in Mobile Application Testing.

\n\n

Readers Guide for using this Book:

\n\n

I have formatted this book in a way to help the readers understand the content very easily.

\n\n

To enable the same each chapter will try to address many of the questions we will have like : What, How, Why, Where, When, Which etc wherever applicable and detail the concept / chapter for you.

\n\n

Also the chapters are detailed in the format of Presentation with detailed pointed explanation will help you understand the chapter better.

\n\n

As the Mobile OS and the testing tools are evolving very fast I have included a section at the beginning of each chapter detailing:

\n\n

What is the supported OS: Common chapter/ IOS / Android etc.

\n\n

What is the version of the Supported OS: IOS 7/Android M/ etc.

\n\n

Technical Knowledge complexity: High/ Medium/ Low.

\n\n

Does this chapter has any practical steps: Yes/No.

\n\n

This will help you understand prepare yourself about the chapter before you start reading them.

\n\n

Chapter-1

\n\n

Mobile App Eco system

\n\n

What is the supported OS

\n\n

Common chapter

\n\n

What is the version of the Supported OS

\n\n

Common chapter

\n\n

Technical Knowledge complexity (High, Medium, Low)

\n\n

Low

\n\n

Does this chapter has any practical steps

\n\n

\n1. 1 Mobile App Eco System

\n\n

¬• Mobile Application been existence for more than a decade. _

\n\n

¬• Many of us experienced seeing how Palm Pilot was used and how Blackberry on its high _years used as the only preferable platform for corporate email communication. Even now _many enterprise uses the Blackberry smartphones for their email.

\n\n

¬• Many of these early devices had the Mobile applications and some even had an SDK for _developers to develop and deliver the apps. _

\n\n

¬• A real Mobile apps revolution started when Apple Introduced the iPhone in 2008 most _importantly when they released the SDK (Software Development Kit) for developers to develop the apps for these devices. - The revolution followed by the release of Google open source Android Mobile Operating system during 2008/2009. Understanding Smartphone Market: _

\n\n

¬• Smartphone Market nothing like PC where more that 80% of the world market is controlled by Microsoft. - From 2008 - 5 years on both IOS (iPhone, iPad devices) and Android contribute to more that 70% of the market share.- Rest of the 30% market is being controlled by Microsoft Windows Phone, Blackberry, Nokia etc. _

\n\n

\n1.1 1.1 Understanding Smartphone OS

\n\n

¬• There are Multiple smartphone Operating systems are available in the market. Part of this Book we will focus on Two prominent OS - IOS and Android.

\n\n

\n1.2 1.2 IOS - introduction

\n\n

¬• IOS (iPhone OS) is promoted by Apple. _

\n\n

¬• Unix based platform - Stripped down version of their MAC OS X os. _

\n\n

¬• Objective-c is supported programming for developing both MAC and IOS based applications. _

\n\n

¬• Latest OS release is IOS7. _

\n\n

¬• Apple controls both Mobile Device Hardware and software development. _

\n\n

¬• Screen size specifications are clearly defined from Apple perspective. _Apple devices. _

\n\n

¬• Apple delivers multiple devices iPhone, iPad, ipad mini, iPad Air.within iPhone we have different size and type of devices (iPhone Retina supporte\\ d,iPhone3GS,iPhone4,5,5s,5cetc).

\n\n

All these devices uses the same IOS as a base **for **their OS. Application created **for **iPhone can very well executed on iPad.

\n\n

\n1.3 1.3 Android - Introduction

\n\n

¬• Android OS is promoted by Google as open source project initiative. _

\n\n

¬• Android apps are created using JAVA (version of JAVA Specific to Android). _

\n\n

¬• Latest OS release is known as KitKat. _Android device variance. - Android being a open source initiative allows OEM (original equipment manufacturers) to control the size of the device. - This Increases various devices sizes supported by many prominent OEM providers like -Samsung, Sony, Dell, HP, HTC etc. _

\n\n

\n1.4 1.4 Mobile Applications - Introduction

\n\n

¬• Both Apple and Google provides the developers SDK (Software Development Kit) to enable them to develop mobile applications. _

\n\n

¬• All the SDK and related tools are provided FREE of cost by both providers. _Constraint on IOS from Apple. - To develop IOS applications developers can get the SDK for free but it will work only on MAC OS. Apple does not provide a windows supported iOS app development. - But from testers perspective windows machines are enough to start testing we will cover them in subsequent chapters. _

\n\n

\n1.5 1.5 Mobile App and their Lifecycle

\n\n

¬• Mobile applications follow development/ Deployment / Distribution lifecycle which are completely different from typical web / windows based application lifecycle. _

\n\n

¬• Most of the web/ windows based applications are deployed for distribution with in the Enterprise premise and with in the enterprise infrastructure. _

\n\n

¬• But for Mobile application targeted to end customers mostly developed and tested with in the enterprise but distribution is completely taken cared by OS Providers. _

\n\n

image - Mobile App Eco System_Mobile App Lifecycle details:

\n\n

¬• Mobile applications once developed and tested ready for deployment are directly submitted to √íApplication Stores√ì of the OS providers for their approval. _

\n\n

¬• Once approved the Mobile applications are available for download from the respective OS providers √íApplication Store√ì. _

\n\n

¬• End customers can directly download your application from these √íApplication stores√ì on their mobile devices to use the same.

\n\n

\n1.5.1 1.5.1 Mobile App store (Market place) _

\n\n

¬• All prominent Mobile OS providers has their app store build and available for use. _

\n\n

¬• Apple IOS - Apple App store. Google Android - Google Play Store Nokia - OVI Market Microsoft, blackberry etc has their own application stores.

\n\n

¬• There are Enterprise / company develop mobile application for their own employees. _

\n\n

¬• In this case companies can have their own √íin-House App Store√ì accessible only with in _enterprise and only for their employees. _

\n\n

\n1.5.2 1.5.2 How the Mobile App Delivery to end customer is controlled _

\n\n

¬• In typical Web / Windows applications the delivery of services will be completely controlled by the enterprise itself. _

\n\n

¬• Interestingly when you deliver the Mobile application to App store by OS providers they control how it is delivered to the end customer. _

\n\n

¬• OS Provides handle complete detail about: Who owns the apps and what activity it does. _

\n\n

¬• When identified of any security / misbehavior of the app the OS providers has final say and _can remove the app from App store.

\n\n

\n1.5.3 _1.5.2.1 How does the OS provider manage the app delivery and ownership details _

\n\n

¬• To answer how the OS providers (Apples and Googles) manage the app ownership detail are done through some think called √íDeveloper Certificates√ì _

\n\n

\n1.5.4 what is developer certificate and when do i need it? _

\n\n

¬• From IOS Perspective: - If you wish to deploy your Application to develop/test on the Mobile device (iPhone, iPad etc). - If you wish to distribute your application to Apple App Store. #### from Android Perspective: - Only required when you wish to distribute the Android app to app store.

\n\n

\n1.5.5 _1.5.3.1 Mobile Application Developer License - Introduction _

\n\n

¬• We mentioned that both Apple and Google providetheirSDK (SoftwareDevelopmentKit) for free. _

\n\n

¬• SDK enables the developers to develop the application for FREE. _

\n\n

¬• But Not the Developer certificate - If the Developer completes the development and wishes _to deliver the App to App store they require to purchase the Developer License Individually _from App store providers. _

\n\n

¬• Below are the details of various app stores and their cost of acquiring the Developer License. _

\n\n

Image - Mobile App Eco System

\n\n

\n1.6 1.5.4 Development and Testing Constraint

\n\n

¬• In Typical Web/ Windows Development the whole environment or near final environment is available for development, testing and distribution / Deployment. _

\n\n

¬• In Mobile App development to develop and test the application do we need to by all the different versions of expensive Hardware (i.e: iPhone,iPad, Android Phone, Android Tab with multiple form factor) to develop and test my app? _

\n\n

¬• The answer is √íNO√ì. _

\n\n

1.5.4.1 IOS and Android Answer to Development / Testing Mobile App challenge** **

\n\n

\n1.6.0.1 _1.5.4.1.1 IOS Simulator: _

\n\n

¬• Apple part of their development SDK provide a software called √íIOS Simulator√ì - Before the application can be tested on the device - Testers can use the Simulator to test the application. _

\n\n

¬• IOS Simulator is a simulation of the IOS Devices and does not guaranteed by Apple that all _the functionality executed on Simulator will work OK on Devices. _

\n\n

¬• As the IOS SDK is only available on MAC machines so does the IOS Simulator - are available only in MAC Machines. ##### Android Emulator. _

\n\n

¬• GooglepartoftheirdevelopmentSDKprovidesasoftwarecalled√íAndroidemulator√ì-Google names it a emulator to depict that it almost mimic the real real on you environment. _

\n\n

¬• Unlike Apple Google Emulators are available for both PC and MAC. _It is recommended that the all features of the mobile Application can be fully tested using simulator but before the app is delivered to App store it is recommended to test on device to make sure that it works OK on the device you are targeting. _

\n\n

\n1.7 1.6 Different Types of Mobile Applications.

\n\n

¬• There are three type of Mobile Application can be created on a border note.

\n\n

Image - Mobile App Eco System 7

\n\n

\n1.8 1.6.1 Native Mobile Applications

\n\n

¬• Mobile Applications build using Native programming language supported by the platform (Apple - Objective-c and Android - JAVA). _

\n\n

¬• The Application created can only be accessed through the OS Providers Application stores. _

\n\n

¬• End customer has to directly download the application from the App store on their devices to _utilize the apps. _

\n\n

¬• Native Mobile applications provide the capability to utilize the device specific hardware _features - i.e: Device camera can be integrated on the Mobile app, Device GPS, Device accelerometer etc. _

\n\n

\n1.9 1.6.2 Mobile Web Applications _

\n\n

¬• We all are familiar with the Desk Top web pages/services. _

\n\n

¬• When we directly access the Desktop web pages on mobile the user experience of the pages _would degrade due to the small real-estate of the Mobile devices. _

\n\n

¬• There are many frameworks available in the market to modify / create web applications that _are fit to specific device accessing the web pages. i.e Twitter Bootstrap, Foundation etc. _

\n\n

¬• BasedonthesizeoftheMobiledeviceaccessingthewebpagethepagecontentwillbetrimmed _to fit to the screen to provide greater user experience. _

\n\n

¬• These Mobile pages are accessed through the Mobile Web Browsers installed on the device. _

\n\n

¬• Mobile web applications does not provide option to integrate the Device hardware features _i.e: Camera, GPS etc.

\n\n

\n1.10 _1.6.3 Hybrid Mobile Applications _

\n\n

¬• There are two variants of the Hybrid mobile applications are defined based on the way it is developed. #### Native Wrapper based Hybrid Mobile apps _

\n\n

¬• UsingthethisapproachtheMobileWebpages/servicesarecreatedusingtypicalHTML,CSS and JAVA Script. _

\n\n

¬• Once created they will be wrapped as Native Applications using some of the frameworks in the Market - i.e: PhoneGap support such hybrid app development. _

\n\n

¬• Advantage of the wrapping mobile applications including developing the service once and wrapping to multiple platforms like IOS, android etc. _

\n\n

¬• This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc. #### Native + web view control based Hybrid Mobile apps _

\n\n

¬• InthisApproachtheMobileapplicationsarecreatedusingtheNativeprogramminglanguage it self. _

\n\n

¬• In Native programming Language both IOS and Android provide a component called - √íWeb View Control√ì. _

\n\n

¬• Web view control enable the web pages to be loaded part of the Mobile Native applications. _

\n\n

¬• This Native applications utilizing the Web view control provide option for developing the Hybrid Mobile applications.

\n\n

¬• This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc.

\n\n

\n2. Mobile App Eco System

\n\n

Mobile OS and Mobile Applications - A Primer.

\n\n

Mobile Application been existence for more than a decade.
Many of us experienced seeing how Palm Pilot was used and how Blackberry on its high years used as the only preferable platform for corporate email communication. Even now many enterprise uses the Blackberry smartphones for their email.
Many of these early devices had the Mobile applications and some even had an SDK for developers to develop and deliver the apps.
A real Mobile apps revolution started when Apple Introduced the iPhone in 2008 most importantly when they released the SDK (Software Development Kit) for developers to develop the apps for these devices.- The revolution followed by the release of Google open source Android Mobile Operating system during 2008/2009.\nUnderstanding SmartPhone Market:\n
SmartPhone Market nothing like PC where more that 80% of the world market is controlled by Microsoft.Â - From 2008 - 5 years on both IOS (iPhone, iPad devices) and Android contribute to more that 70% of the market share.- Rest of the 30% market is being controlled by Microsoft Windows Phone, Blackberry, Nokia etc.

\n\n

\n2.1 Understanding SmartPhone OS

There are Multiple smartphone Operating systems are available in the market. Part of this Book we will focus on Two prominent OS - IOS and Android.

\n\n

\n2.2 IOS - introduction

\n\n

IOS (iPhone OS) is promoted by Apple.
Unix based platform - Stripped down version of their MAC OS X os.
Objective-c is supported programming for developing both MAC and IOS based applications.
Latest OS release is IOS7.
Apple controls both Mobile Device Hardware and software development.
Screen size specifications are clearly defined from Apple perspective.

\n\n\n\n

1  Apple delivers multiple devices iPhone, iPad, ipad mini, iPad Air. \n2  within iPhone we have different size and type of devices (iPhone Retina support\\\n3 ed, iPhone 3GS, iPhone 4, 5, 5s, 5c etc). \n4  All these devices uses the same IOS as a base for their OS. \n5  Application created for iPhone can very well executed on iPad. \n

\n\n\n\n

\n2.3 Android - Introduction

\n\n

Android OS is promoted by Google as open source project initiative.
Android apps are created using JAVA (version of JAVA Specific to Android).
Latest OS release is known as KitKat.

\n\n\n\n

\n2.4 Mobile Applications - Introduction

\n\n

Both Apple and Google provides the developers SDK (Software Development Kit) to enable them to develop mobile applications.
All the SDK and related tools are provided FREE of cost by both providers.

\n\n\n\n

\n2.5 Mobile App and their Lifecycle

Mobile applications follow development/ Deployment / Distribution lifecycle which are completely different from typical web / windows based application lifecycle.
Most of the web/ windows based applications are deployed for distribution with in the Enterprise premise and with in the enterprise infrastructure.
But for Mobile application targeted to end customers mostly developed and tested with in the enterprise but distribution is completely taken cared by OS Providers.

\n\n

Mobile App Lifecycle details:

\n\n\n

Mobile applications once developed and tested ready for deployment are directly submitted to “Application Stores” of the OS providers for their approval.
Once approved the Mobile applications are available for download from the respective OS providers “Application Store”.
End customers can directly download your application from these “Application stores” on their mobile devices to use the same.

\n\n

\n2.5.1 Mobile App store (Market place)

\n\n

All prominent Mobile OS providers has their app store build and available for use.

\n\n

Apple IOS \t\t\t- Apple App store.\nGoogle Android\t\t- Google Play Store\nNokia\t\t\t\t- OVI Market\nMicrosoft, blackberry etc has their own application stores.

\n\n

There are Enterprise / company develop mobile application for their own employees.
In this case companies can have their own “in-House App Store” accessible only with in enterprise and only for their employees.

\n\n

\n2.5.2 How the Mobile App Delivery to end customer is controlled

\n\n

In typical Web / Windows applications the delivery of services will be completely controlled by the enterprise itself.
Interestingly when you deliver the Mobile application to App store by OS providers they control how it is delivered to the end customer.
OS Provides handle complete detail about: Who owns the apps and what activity it does.
When identified of any security / misbehavior of the app the OS providers has final say and can remove the app from App store.

\n\n

\n2.5.2.1 How does the OS provider manage the app delivery and ownership details

To answer how the OS providers (Apples and Googles) manage the app ownership detail are done through some think called “Developer Certificates”

\n\n

\n2.5.3 what is developer certificate and when do i need it?

#### From IOS Perspective:\n- If you wish to deploy your Application to develop/test on the Mobile device (iPhone, iPad etc).\n- If you wish to distribute your application to Apple App Store.\n#### from Android Perspective:\n- Only required when you wish to distribute the Android app to app store.

\n\n

\n2.5.3.1 Mobile Application Developer License - Introduction

\n\n

We mentioned that both Apple and Google provide their SDK (Software Development Kit) for free.
SDK enables the developers to develop the application for FREE.
But Not the Developer certificate - If the Developer completes the development and wishes to deliver the App to App store they require to purchase the Developer License Individually from App store providers.
Below are the details of various app stores and their cost of acquiring the Developer License.

\n\n\n

\n2.5.4 Development and Testing Constraint

In Typical Web/ Windows Development the whole environment or near final environment is available for development, testing and distribution / Deployment.
In Mobile App development to develop and test the application do we need to by all the different versions of expensive Hardware (i.e: iPhone,iPad, Android Phone, Android Tab with multiple form factor) to develop and test my app?
The answer is “NO”.

\n\n

\n2.5.4.1 IOS and Android Answer to Development / Testing Mobile App challenge

\n\n

\n2.5.4.1.1 IOS Simulator:

Apple part of their development SDK provide a software called “IOS Simulator” - Before the application can be tested on the device - Testers can use the Simulator to test the application.
IOS Simulator is a simulation of the IOS Devices and does not guaranteed by Apple that all the functionality executed on Simulator will work OK on Devices.
As the IOS SDK is only available on MAC machines so does the IOS Simulator - are available only in MAC Machines.\n##### Android Emulator.
Google part of their development SDK provides a software called “Android emulator” - Google names it a emulator to depict that it almost mimic the real real on you environment.
Unlike Apple Google Emulators are available for both PC and MAC.

\n\n\n\n

\n2.6 Different Types of Mobile Applications.

\n\n

There are three type of Mobile Application can be created on a border note.

\n\n\n

\n2.6.1 Native Mobile Applications

Mobile Applications build using Native programming language supported by the platform (Apple - Objective-c and Android - JAVA).
The Application created can only be accessed through the OS Providers Application stores.
End customer has to directly download the application from the App store on their devices to utilize the apps.
Native Mobile applications provide the capability to utilize the device specific hardware features - i.e: Device camera can be integrated on the Mobile app, Device GPS, Device accelerometer etc.

\n\n

\n2.6.2 Mobile Web Applications

We all are familiar with the Desk Top web pages/services.
When we directly access the Desktop web pages on mobile the user experience of the pages would degrade due to the small real-estate of the Mobile devices.
There are many frameworks available in the market to modify / create web applications that are fit to specific device accessing the web pages. i.e Twitter Bootstrap, Foundation etc.
Based on the size of the Mobile device accessing the web page the page content will be trimmed to fit to the screen to provide greater user experience.
These Mobile pages are accessed through the Mobile Web Browsers installed on the device.
Mobile web applications does not provide option to integrate the Device hardware features i.e: Camera, GPS etc.

\n\n

\n2.6.3 Hybrid Mobile Applications

There are two variants of the Hybrid mobile applications are defined based on the way it is developed.\n#### Native Wrapper based Hybrid Mobile apps
Using the this approach the Mobile Web pages / services are created using typical HTML, CSS and JAVA Script.
Once created they will be wrapped as Native Applications using some of the frameworks in the Market - i.e: PhoneGap support such hybrid app development.
Advantage of the wrapping mobile applications including developing the service once and wrapping to multiple platforms like IOS, android etc.
This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc.\n#### Native + web view control based Hybrid Mobile apps
In this Approach the Mobile applications are created using the Native programming language it self.
In Native programming Language both IOS and Android provide a component called - “Web View Control”.
Web view control enable the web pages to be loaded part of the Mobile Native applications.
This Native applications utilizing the Web view control provide option for developing the Hybrid Mobile applications.
This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc.

\n\n

\n3. Mobile App Testing Primer

\n\n

\n3.0.1 “Smart” features of Smartphone.

\n\n

In this section we will detail majority of the “Smart” features that make the smartphone real smarter.
Before testers approach the App testing they need to understand all the Smart features of the latest SmartPhone OS.
Below are some of the prominently used Smart Phone features integrated with the Mobile Applications.

\n\n\n

\n\n\n\n

\n\n\n

\n4. User Experience Testing Mobile App

\n\n

To make a preview of your book, click on the “Preview” button on the left. We’ll show you some links to download your book when the preview is complete.

\n\n

You can keep writing in the meantime.

\n\n

That’s it for the brief introduction to Leanpub.

\n\n

\n5. Automation Testing tool primer

\n\n

\n6. Distributing Mobile Apps

\n\n

\n7. IOS App Testing Deep Dive

\n\n

\n7.0.1 IOS Simulator - Deep Dive

\n\n

\n7.0.1.1 Accessing IOS Simulator

\n\n

\n7.0.1.2 Understanding features of IOS Simulator

\n\n\n

\n\n\n\n

\n\n\n

\n8. IOS Application Testing using Simulator

\n\n

\n9. Automation Testing IOS Apps using Instruments

\n\n

\n10. Instruments Basics:\n

\n\n

Instrument is a Free tool provided by Apple part of the IOS SDK Installation.
It provides option to create the automation scripts using record and Play back Option.
The script generated will use the Javascript as programming language.
Supports both IOS device based and IOS Simulator based testing.
Available only on MAC supports only IOS based application automation testing.
How to Access Instrument on MAC.

\n\n\n

\"Screen- — Screen- How to access the Instruments on MAC.

\n\n\n

How to Choose the App to be tested on instruments using “Choose Target”.

\n\n\n

Choosing the App to be tested on Simulator.

\n\n\n

Choosing the App to be tested from Device.

\n\n\n

\"Screen-Choosing — Screen-Choosing the Device Target for Device based testing.

\n\n\n

Enabling script creation.

\n\n\n

\"Screen-Enabling — Screen-Enabling Script Creation.

\n\n\n

Enabling Auto recording the Instruments Script.

\n\n\n

Re-Running the Script.

\n\n\n

Instruments JAVASCRIPT Basics:

\n\n

\n11. Automation Testing IOS Apps using Monkey Talk

\n\n

\n11.1 MonkeyTalk Introduction

\n\n

\n11.2 MonkeyTalk IDE

\n\n\n

\n\n\n\n

\n\n\n

\n12. Performance Testing IOS Apps

\n\n

\n13. Android App Testing Deep Dive

\n\n

\n14. Android App Testing using Emulator

\n\n

\n15. Automation Testing Android apps using Robotium

\n\n

\n16. Automation Testing Android apps using Monkey Talk

\n\n

\n17. Performance Testing Android Apps’

\n\n

\n18. Security Testing Mobile Apps a Primer

\n\n

\n19. IOS Apps Security Testing

\n\n

\n20. Android Apps Security Testing

\n\n

\n21. Cloud Based Automation Testing

\n\n

\n22. Mobile Web App testing

\n\n

\n23. Converted Files

\n\n

\n23.1 Practical approach to mobile application testing Book v0.1

\n\n

Om namo Narayana.

\n\n

Table of content:

\n\n

Mobile App Eco system
Mobile App Testing Primer
Mobile Testing Strategy
Testing Native Android Application Basics.
Testing Native IOS Application Basics
Automation Testing Tools Primer
IOS Native Application Testing √ê Deep Dive
Automation Testing IOS Application using Instruments
IOS Application Performance Testing

\n\n

10.IOS Application security Testing

\n\n

11.Android Native Application Testing √ê Deep Dive

\n\n

12.Android Automation Testing using Robotium

\n\n

13.Android Performance Testing

\n\n

14.Android Security Testing

\n\n

15.IOS and Android Automation Testing using Appium

\n\n

16.Mobile Web Application Testing

\n\n

17.Cloud Based Automation Testing Tools introduction

\n\n

18.Recent advancement in Mobile Application Testing.

\n\n

Readers Guide for using this Book:

\n\n

I have formatted this book in a way to help the readers understand the content very easily.

\n\n

To enable the same each chapter will try to address many of the questions we will have like : What, How, Why, Where, When, Which etc wherever applicable and detail the concept / chapter for you.

\n\n

Also the chapters are detailed in the format of Presentation with detailed pointed explanation will help you understand the chapter better.

\n\n

As the Mobile OS and the testing tools are evolving very fast I have included a section at the beginning of each chapter detailing:

\n\n

What is the supported OS: Common chapter/ IOS / Android etc.

\n\n

What is the version of the Supported OS: IOS 7/Android M/ etc.

\n\n

Technical Knowledge complexity: High/ Medium/ Low.

\n\n

Does this chapter has any practical steps: Yes/No.

\n\n

This will help you understand prepare yourself about the chapter before you start reading them.

\n\n

Chapter-1

\n\n

Mobile App Eco system

\n\n

What is the supported OS

\n\n

Common chapter

\n\n

What is the version of the Supported OS

\n\n

Common chapter

\n\n

Technical Knowledge complexity (High, Medium, Low)

\n\n

Low

\n\n

Does this chapter has any practical steps

\n\n

\n24. 1 Mobile App Eco System

\n\n

¬• Mobile Application been existence for more than a decade. _

\n\n

¬• Many of these early devices had the Mobile applications and some even had an SDK for _developers to develop and deliver the apps. _

\n\n

\n24.1 1.1 Understanding Smartphone OS

\n\n

¬• There are Multiple smartphone Operating systems are available in the market. Part of this Book we will focus on Two prominent OS - IOS and Android.

\n\n

\n24.2 1.2 IOS - introduction

\n\n

¬• IOS (iPhone OS) is promoted by Apple. _

\n\n

¬• Unix based platform - Stripped down version of their MAC OS X os. _

\n\n

¬• Objective-c is supported programming for developing both MAC and IOS based applications. _

\n\n

¬• Latest OS release is IOS7. _

\n\n

¬• Apple controls both Mobile Device Hardware and software development. _

\n\n

¬• Screen size specifications are clearly defined from Apple perspective. _Apple devices. _

\n\n

¬• Apple delivers multiple devices iPhone, iPad, ipad mini, iPad Air.within iPhone we have different size and type of devices (iPhone Retina supporte\\ d,iPhone3GS,iPhone4,5,5s,5cetc).

\n\n

All these devices uses the same IOS as a base **for **their OS. Application created **for **iPhone can very well executed on iPad.

\n\n

\n24.3 1.3 Android - Introduction

\n\n

¬• Android OS is promoted by Google as open source project initiative. _

\n\n

¬• Android apps are created using JAVA (version of JAVA Specific to Android). _

\n\n

\n24.4 1.4 Mobile Applications - Introduction

\n\n

¬• Both Apple and Google provides the developers SDK (Software Development Kit) to enable them to develop mobile applications. _

\n\n

\n24.5 1.5 Mobile App and their Lifecycle

\n\n

¬• Mobile applications follow development/ Deployment / Distribution lifecycle which are completely different from typical web / windows based application lifecycle. _

\n\n

¬• Most of the web/ windows based applications are deployed for distribution with in the Enterprise premise and with in the enterprise infrastructure. _

\n\n

¬• But for Mobile application targeted to end customers mostly developed and tested with in the enterprise but distribution is completely taken cared by OS Providers. _

\n\n

image - Mobile App Eco System_Mobile App Lifecycle details:

\n\n

¬• Mobile applications once developed and tested ready for deployment are directly submitted to √íApplication Stores√ì of the OS providers for their approval. _

\n\n

¬• Once approved the Mobile applications are available for download from the respective OS providers √íApplication Store√ì. _

\n\n

¬• End customers can directly download your application from these √íApplication stores√ì on their mobile devices to use the same.

\n\n

\n24.5.1 1.5.1 Mobile App store (Market place) _

\n\n

¬• All prominent Mobile OS providers has their app store build and available for use. _

\n\n

¬• Apple IOS - Apple App store. Google Android - Google Play Store Nokia - OVI Market Microsoft, blackberry etc has their own application stores.

\n\n

¬• There are Enterprise / company develop mobile application for their own employees. _

\n\n

¬• In this case companies can have their own √íin-House App Store√ì accessible only with in _enterprise and only for their employees. _

\n\n

\n24.5.2 1.5.2 How the Mobile App Delivery to end customer is controlled _

\n\n

¬• In typical Web / Windows applications the delivery of services will be completely controlled by the enterprise itself. _

\n\n

¬• Interestingly when you deliver the Mobile application to App store by OS providers they control how it is delivered to the end customer. _

\n\n

¬• OS Provides handle complete detail about: Who owns the apps and what activity it does. _

\n\n

¬• When identified of any security / misbehavior of the app the OS providers has final say and _can remove the app from App store.

\n\n

\n24.5.3 _1.5.2.1 How does the OS provider manage the app delivery and ownership details _

\n\n

¬• To answer how the OS providers (Apples and Googles) manage the app ownership detail are done through some think called √íDeveloper Certificates√ì _

\n\n

\n24.5.4 what is developer certificate and when do i need it? _

\n\n

\n24.5.5 _1.5.3.1 Mobile Application Developer License - Introduction _

\n\n

¬• We mentioned that both Apple and Google providetheirSDK (SoftwareDevelopmentKit) for free. _

\n\n

¬• SDK enables the developers to develop the application for FREE. _

\n\n

¬• Below are the details of various app stores and their cost of acquiring the Developer License. _

\n\n

Image - Mobile App Eco System

\n\n

\n24.6 1.5.4 Development and Testing Constraint

\n\n

¬• In Typical Web/ Windows Development the whole environment or near final environment is available for development, testing and distribution / Deployment. _

\n\n

¬• The answer is √íNO√ì. _

\n\n

1.5.4.1 IOS and Android Answer to Development / Testing Mobile App challenge** **

\n\n

\n24.6.0.1 _1.5.4.1.1 IOS Simulator: _

\n\n

¬• IOS Simulator is a simulation of the IOS Devices and does not guaranteed by Apple that all _the functionality executed on Simulator will work OK on Devices. _

\n\n

¬• As the IOS SDK is only available on MAC machines so does the IOS Simulator - are available only in MAC Machines. ##### Android Emulator. _

\n\n

¬• GooglepartoftheirdevelopmentSDKprovidesasoftwarecalled√íAndroidemulator√ì-Google names it a emulator to depict that it almost mimic the real real on you environment. _

\n\n

\n24.7 1.6 Different Types of Mobile Applications.

\n\n

¬• There are three type of Mobile Application can be created on a border note.

\n\n

Image - Mobile App Eco System 7

\n\n

\n24.8 1.6.1 Native Mobile Applications

\n\n

¬• Mobile Applications build using Native programming language supported by the platform (Apple - Objective-c and Android - JAVA). _

\n\n

¬• The Application created can only be accessed through the OS Providers Application stores. _

\n\n

¬• End customer has to directly download the application from the App store on their devices to _utilize the apps. _

\n\n

\n24.9 1.6.2 Mobile Web Applications _

\n\n

¬• We all are familiar with the Desk Top web pages/services. _

\n\n

¬• When we directly access the Desktop web pages on mobile the user experience of the pages _would degrade due to the small real-estate of the Mobile devices. _

\n\n

¬• There are many frameworks available in the market to modify / create web applications that _are fit to specific device accessing the web pages. i.e Twitter Bootstrap, Foundation etc. _

\n\n

¬• BasedonthesizeoftheMobiledeviceaccessingthewebpagethepagecontentwillbetrimmed _to fit to the screen to provide greater user experience. _

\n\n

¬• These Mobile pages are accessed through the Mobile Web Browsers installed on the device. _

\n\n

¬• Mobile web applications does not provide option to integrate the Device hardware features _i.e: Camera, GPS etc.

\n\n

\n24.10 _1.6.3 Hybrid Mobile Applications _

\n\n

¬• There are two variants of the Hybrid mobile applications are defined based on the way it is developed. #### Native Wrapper based Hybrid Mobile apps _

\n\n

¬• UsingthethisapproachtheMobileWebpages/servicesarecreatedusingtypicalHTML,CSS and JAVA Script. _

\n\n

¬• Once created they will be wrapped as Native Applications using some of the frameworks in the Market - i.e: PhoneGap support such hybrid app development. _

\n\n

¬• Advantage of the wrapping mobile applications including developing the service once and wrapping to multiple platforms like IOS, android etc. _

\n\n

¬• This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc. #### Native + web view control based Hybrid Mobile apps _

\n\n

¬• InthisApproachtheMobileapplicationsarecreatedusingtheNativeprogramminglanguage it self. _

\n\n

¬• In Native programming Language both IOS and Android provide a component called - √íWeb View Control√ì. _

\n\n

¬• Web view control enable the web pages to be loaded part of the Mobile Native applications. _

\n\n

¬• This Native applications utilizing the Web view control provide option for developing the Hybrid Mobile applications.

\n\n

¬• This approach also provides option to integrate with Native Mobile device Hardware features like Camera, GPS etc.

\n\n\n

\n\n","tocStructure",[300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352],{"_71":72,"_38":73,"_65":-5,"_74":75,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":81,"_65":-5,"_74":82,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":87,"_65":-5,"_74":88,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":90,"_65":-5,"_74":91,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":93,"_65":-5,"_74":94,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":96,"_65":-5,"_74":97,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":99,"_65":-5,"_74":100,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":102,"_65":-5,"_74":103,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":105,"_65":-5,"_74":106,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":108,"_65":-5,"_74":109,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":111,"_65":-5,"_74":112,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":114,"_65":-5,"_74":115,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":118,"_65":-5,"_74":119,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":121,"_65":-5,"_74":122,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":124,"_65":-5,"_74":125,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":127,"_65":-5,"_74":128,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":130,"_65":-5,"_74":131,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":133,"_65":-5,"_74":134,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":136,"_65":-5,"_74":137,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":140,"_65":-5,"_74":141,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":144,"_65":-5,"_74":145,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":148,"_65":-5,"_74":149,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":152,"_65":-5,"_74":153,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":156,"_65":-5,"_74":157,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":160,"_65":-5,"_74":161,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":164,"_65":-5,"_74":165,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":168,"_65":-5,"_74":169,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":172,"_65":-5,"_74":173,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":175,"_65":-5,"_74":176,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":178,"_65":-5,"_74":179,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":182,"_65":-5,"_74":183,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":186,"_65":-5,"_74":187,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":190,"_65":-5,"_74":191,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":194,"_65":-5,"_74":195,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":198,"_65":-5,"_74":199,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":202,"_65":-5,"_74":203,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":206,"_65":-5,"_74":207,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":210,"_65":-5,"_74":211,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":214,"_65":-5,"_74":215,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":218,"_65":-5,"_74":219,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":222,"_65":-5,"_74":223,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":226,"_65":-5,"_74":227,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":72,"_38":229,"_65":-5,"_74":230,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":233,"_65":-5,"_74":234,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":236,"_65":-5,"_74":237,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":239,"_65":-5,"_74":240,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":242,"_65":-5,"_74":243,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":245,"_65":-5,"_74":246,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":248,"_65":-5,"_74":249,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":251,"_65":-5,"_74":252,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":254,"_65":-5,"_74":255,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":257,"_65":-5,"_74":258,"_67":76,"_83":-5,"_84":-5,"_85":-5},{"_71":80,"_38":260,"_65":-5,"_74":261,"_67":76,"_83":-5,"_84":-5,"_85":-5},"publicChapterContent","nextChapter","sections",[327,328],"routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

\n11. Automation Testing IOS Apps using Monkey Talk

\n11.1 MonkeyTalk Introduction

\n11.2 MonkeyTalk IDE

Table of Contents

\n0.1 Practical approach to mobile application testing Book v0.1

\n1. 1 Mobile App Eco System

\n1.1 1.1 Understanding Smartphone OS

\n1.2 1.2 IOS - introduction

\n1.3 1.3 Android - Introduction

\n1.4 1.4 Mobile Applications - Introduction

\n1.5 1.5 Mobile App and their Lifecycle

\n1.5.1 1.5.1 Mobile App store (Market place) _

\n1.5.2 1.5.2 How the Mobile App Delivery to end customer is controlled _

\n1.5.3 _1.5.2.1 How does the OS provider manage the app delivery and ownership details _

\n1.5.4 what is developer certificate and when do i need it? _

\n1.5.5 _1.5.3.1 Mobile Application Developer License - Introduction _

\n1.6 1.5.4 Development and Testing Constraint

\n1.6.0.1 _1.5.4.1.1 IOS Simulator: _

\n1.7 1.6 Different Types of Mobile Applications.

\n1.8 1.6.1 Native Mobile Applications

\n1.9 1.6.2 Mobile Web Applications _

\n1.10 _1.6.3 Hybrid Mobile Applications _

\n2. Mobile App Eco System

\n2.1 Understanding SmartPhone OS

\n2.2 IOS - introduction

\n2.3 Android - Introduction

\n2.4 Mobile Applications - Introduction

\n2.5 Mobile App and their Lifecycle

\n2.5.1 Mobile App store (Market place)

\n2.5.2 How the Mobile App Delivery to end customer is controlled

\n2.5.2.1 How does the OS provider manage the app delivery and ownership details

\n2.5.3 what is developer certificate and when do i need it?

\n2.5.3.1 Mobile Application Developer License - Introduction

\n2.5.4 Development and Testing Constraint

\n2.5.4.1 IOS and Android Answer to Development / Testing Mobile App challenge

\n2.5.4.1.1 IOS Simulator:

\n2.6 Different Types of Mobile Applications.

\n2.6.1 Native Mobile Applications

\n2.6.2 Mobile Web Applications

\n2.6.3 Hybrid Mobile Applications

\n3. Mobile App Testing Primer

\n3.0.1 “Smart” features of Smartphone.

\n4. User Experience Testing Mobile App

\n5. Automation Testing tool primer

\n6. Distributing Mobile Apps

\n7. IOS App Testing Deep Dive

\n7.0.1 IOS Simulator - Deep Dive

\n7.0.1.1 Accessing IOS Simulator

\n7.0.1.2 Understanding features of IOS Simulator

\n8. IOS Application Testing using Simulator

\n9. Automation Testing IOS Apps using Instruments

\n10. Instruments Basics:\n

\n11. Automation Testing IOS Apps using Monkey Talk

\n11.1 MonkeyTalk Introduction

\n11.2 MonkeyTalk IDE

\n12. Performance Testing IOS Apps

\n13. Android App Testing Deep Dive

\n14. Android App Testing using Emulator

\n15. Automation Testing Android apps using Robotium

\n16. Automation Testing Android apps using Monkey Talk

\n17. Performance Testing Android Apps’

\n18. Security Testing Mobile Apps a Primer

\n19. IOS Apps Security Testing

\n20. Android Apps Security Testing

\n21. Cloud Based Automation Testing

\n22. Mobile Web App testing

\n23. Converted Files

\n23.1 Practical approach to mobile application testing Book v0.1

\n24. 1 Mobile App Eco System

\n24.1 1.1 Understanding Smartphone OS

\n24.2 1.2 IOS - introduction

\n24.3 1.3 Android - Introduction

\n24.4 1.4 Mobile Applications - Introduction

\n24.5 1.5 Mobile App and their Lifecycle

\n24.5.1 1.5.1 Mobile App store (Market place) _

\n24.5.2 1.5.2 How the Mobile App Delivery to end customer is controlled _

\n24.5.3 _1.5.2.1 How does the OS provider manage the app delivery and ownership details _

\n24.5.4 what is developer certificate and when do i need it? _

\n24.5.5 _1.5.3.1 Mobile Application Developer License - Introduction _

\n24.6 1.5.4 Development and Testing Constraint