Introduction to Mobile Application Testing:
Gone are the days when the telephone used to be an appliance that sat in a corner and had to ring to get our attention or a computer was a machine only few people used – they are now an extension of our being- a window to the world and virtual servants that do as they are told. Computers were a rage and changed how we humans thought, behaved, learnt and existed.
Mobile technology and smart devices are the trend now and will change the future of the world as we know it. We all can vouch for it, can’t we? Now, it will be amateurish if I list what we use these mobile devices for. You all know it – May be better than we do
Types of Mobile Testing
There are broadly 2 kinds of testing that take place on mobile devices:
#1. Hardware testing:
The device including the internal processors, internal hardware, screen sizes, resolution, space or memory, camera, radio, Bluetooth, WIFI etc. This is sometimes referred to as, simple “Mobile Testing”.
#2. Software or Application testing:
The applications that work on mobile devices and their functionality is tested. It is called the “Mobile Application Testing” to differentiate it from the earlier method. Even in the mobile applications, there are few basic differences that are important to understand:
a) Native apps: A native application is created for use on a platform like mobile and tablets.
b) Mobile web apps are server-side apps to access website/s on mobile using different browsers like chrome, Firefox by connecting to a mobile network or wireless network like WIFI.
c) Hybrid apps are combinations of native app and web app. They run on devices or offline and are written using web technologies like HTML5 and CSS.
There are few basic differences that set these apart:
Native apps have single platform affinity while mobile web apps have cross platform affinity.
Native apps are written in platforms like SDKs while Mobile web apps are written with web technologies like html, css, asp.net, java, php.
For a native app, installation is required but for mobile web apps, no installation is required.
Native app can be updated from play store or app store while mobile web apps are centralized updates.
Many native app don’t require Internet connection but for mobile web apps it’s a must.
Native app works faster when compared to mobile web apps.
Native apps are installed from app stores like Google play store or app store where mobile web are websites and are only accessible through Internet.
The rest of the article is going to be about Mobile Application Testing.
Significance of Mobile Application Testing
Testing applications on mobile devices is more challenging than testing web apps on desktop due to
Different range of mobile devices with different screen sizes and hardware configurations like hard keypad, virtual keypad (touch screen) and trackball etc.
Wide varieties of mobile devices like HTC, Samsung, Apple and Nokia.
Different mobile operating systems like Android, Symbian, Windows, Blackberry and IOS.
Different versions of operation system like iOS 5.x, iOS 6.x, BB5.x, BB6.x etc.
Different mobile network operators like GSM and CDMA.
Frequent updates – (like android- 4.2, 4.3, 4.4, iOS-5.x, 6.x) – with each update a new testing cycle is recommended to make sure no application functionality is impacted.
As with any application, Mobile application testing is also very important, as clientele is usually in millions for a certain product – and a product with bugs is never appreciated. It often results in monetary losses, legal issue and irreparable brand image damage.
Basic Difference Between Mobile and Desktop Application Testing:
Few obvious aspects that sets mobile app testing apart from the desktop testing
On desktop, the application is tested on a central processing unit. On a mobile device, the application is tested on handsets like Samsung, Nokia, Apple and HTC.
Mobile device screen size is smaller than desktop.
Mobile devices have less memory than desktop.
Mobiles use network connections like 2G, 3G, 4G or WIFI where desktop use broadband or dial up connections.
The automation tool used for desktop application testing might not work on mobile applications.
Types of Mobile App Testing:
To address all the above technical aspects, the following types of testing are performed on Mobile applications.
Usability testing- To make sure that the mobile app is easy to use and provides a satisfactory user experience to the customers
Compatibility testing- Testing of the application in different mobiles devices, browsers, screen sizes and OS versions according to the requirements.
Interface testing- Testing of menu options, buttons, bookmarks, history, settings, and navigation flow of the application.
Services testing- Testing the services of the application online and offline.
Low level resource testing: Testing of memory usage, auto deletion of temporary files, local database growing issues known as low level resource testing.
Performance testing- Testing the performance of the application by changing the connection from 2G, 3G to WIFI, sharing the documents, battery consumption, etc.
Operational testing- Testing of backups and recovery plan if battery goes down, or data loss while upgrading the application from store.
Installation tests- Validation of the application by installing /uninstalling it on the devices.
Security Testing- Testing an application to validate if the information system protects data or not.
Mobile Application Testing Strategy
The Test strategy should make sure that all the quality and performance guidelines are met. A few pointers in this area:
1) Selection of the devices - Analyze the market and choose the devices that are widely used. (This decision mostly relies on the clients. The client or the app builders consider the popularity factor of a certain devices as well as the marketing needs for the application to decide what handsets to use for testing.)
2) Emulators – The use of these is extremely useful in the initial stages of development, as they allow quick and efficient checking of the app. Emulator is a system that runs software from one environment to another environment without changing the software itself. It duplicates the features and work on real system.
Types of Mobile Emulators
Device Emulator- provided by device manufacturers
Browser Emulator- simulates mobile browser environments.
Operating systems Emulator- Apple provides emulators for iPhones, Microsoft for Windows phones and Google Android phones
Gone are the days when the telephone used to be an appliance that sat in a corner and had to ring to get our attention or a computer was a machine only few people used – they are now an extension of our being- a window to the world and virtual servants that do as they are told. Computers were a rage and changed how we humans thought, behaved, learnt and existed.
Mobile technology and smart devices are the trend now and will change the future of the world as we know it. We all can vouch for it, can’t we? Now, it will be amateurish if I list what we use these mobile devices for. You all know it – May be better than we do
Types of Mobile Testing
There are broadly 2 kinds of testing that take place on mobile devices:
#1. Hardware testing:
The device including the internal processors, internal hardware, screen sizes, resolution, space or memory, camera, radio, Bluetooth, WIFI etc. This is sometimes referred to as, simple “Mobile Testing”.
#2. Software or Application testing:
The applications that work on mobile devices and their functionality is tested. It is called the “Mobile Application Testing” to differentiate it from the earlier method. Even in the mobile applications, there are few basic differences that are important to understand:
a) Native apps: A native application is created for use on a platform like mobile and tablets.
b) Mobile web apps are server-side apps to access website/s on mobile using different browsers like chrome, Firefox by connecting to a mobile network or wireless network like WIFI.
c) Hybrid apps are combinations of native app and web app. They run on devices or offline and are written using web technologies like HTML5 and CSS.
There are few basic differences that set these apart:
Native apps have single platform affinity while mobile web apps have cross platform affinity.
Native apps are written in platforms like SDKs while Mobile web apps are written with web technologies like html, css, asp.net, java, php.
For a native app, installation is required but for mobile web apps, no installation is required.
Native app can be updated from play store or app store while mobile web apps are centralized updates.
Many native app don’t require Internet connection but for mobile web apps it’s a must.
Native app works faster when compared to mobile web apps.
Native apps are installed from app stores like Google play store or app store where mobile web are websites and are only accessible through Internet.
The rest of the article is going to be about Mobile Application Testing.
Significance of Mobile Application Testing
Testing applications on mobile devices is more challenging than testing web apps on desktop due to
Different range of mobile devices with different screen sizes and hardware configurations like hard keypad, virtual keypad (touch screen) and trackball etc.
Wide varieties of mobile devices like HTC, Samsung, Apple and Nokia.
Different mobile operating systems like Android, Symbian, Windows, Blackberry and IOS.
Different versions of operation system like iOS 5.x, iOS 6.x, BB5.x, BB6.x etc.
Different mobile network operators like GSM and CDMA.
Frequent updates – (like android- 4.2, 4.3, 4.4, iOS-5.x, 6.x) – with each update a new testing cycle is recommended to make sure no application functionality is impacted.
As with any application, Mobile application testing is also very important, as clientele is usually in millions for a certain product – and a product with bugs is never appreciated. It often results in monetary losses, legal issue and irreparable brand image damage.
Basic Difference Between Mobile and Desktop Application Testing:
Few obvious aspects that sets mobile app testing apart from the desktop testing
On desktop, the application is tested on a central processing unit. On a mobile device, the application is tested on handsets like Samsung, Nokia, Apple and HTC.
Mobile device screen size is smaller than desktop.
Mobile devices have less memory than desktop.
Mobiles use network connections like 2G, 3G, 4G or WIFI where desktop use broadband or dial up connections.
The automation tool used for desktop application testing might not work on mobile applications.
Types of Mobile App Testing:
To address all the above technical aspects, the following types of testing are performed on Mobile applications.
Usability testing- To make sure that the mobile app is easy to use and provides a satisfactory user experience to the customers
Compatibility testing- Testing of the application in different mobiles devices, browsers, screen sizes and OS versions according to the requirements.
Interface testing- Testing of menu options, buttons, bookmarks, history, settings, and navigation flow of the application.
Services testing- Testing the services of the application online and offline.
Low level resource testing: Testing of memory usage, auto deletion of temporary files, local database growing issues known as low level resource testing.
Performance testing- Testing the performance of the application by changing the connection from 2G, 3G to WIFI, sharing the documents, battery consumption, etc.
Operational testing- Testing of backups and recovery plan if battery goes down, or data loss while upgrading the application from store.
Installation tests- Validation of the application by installing /uninstalling it on the devices.
Security Testing- Testing an application to validate if the information system protects data or not.
Mobile Application Testing Strategy
The Test strategy should make sure that all the quality and performance guidelines are met. A few pointers in this area:
1) Selection of the devices - Analyze the market and choose the devices that are widely used. (This decision mostly relies on the clients. The client or the app builders consider the popularity factor of a certain devices as well as the marketing needs for the application to decide what handsets to use for testing.)
2) Emulators – The use of these is extremely useful in the initial stages of development, as they allow quick and efficient checking of the app. Emulator is a system that runs software from one environment to another environment without changing the software itself. It duplicates the features and work on real system.
Types of Mobile Emulators
Device Emulator- provided by device manufacturers
Browser Emulator- simulates mobile browser environments.
Operating systems Emulator- Apple provides emulators for iPhones, Microsoft for Windows phones and Google Android phones
Outstanding blog.You can now get best services for software testing and Mobile App promotion at Salvus App Solutions which offers you services for software testing, SEO, ASO, etc. Visit us at- http://salvusappsolutions.com
ReplyDelete