Scribd
Upload
22 views19 pages

Session 5 - Mobile Testing

The document provides an overview of mobile testing fundamentals, focusing on different application types (web-based, native, and hybrid) and their implications for testing. It includes a comprehensive mobile testing checklist, highlights the differences between builds and releases, and offers tips for effective testing. Additionally, it introduces Apple's TestFlight as a tool for distributing beta apps for testing purposes.

Uploaded by

raghad mustafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views19 pages

Session 5 - Mobile Testing

The document provides an overview of mobile testing fundamentals, focusing on different application types (web-based, native, and hybrid) and their implications for testing. It includes a comprehensive mobile testing checklist, highlights the differences between builds and releases, and offers tips for effective testing. Additionally, it introduces Apple's TestFlight as a tool for distributing beta apps for testing purposes.

Uploaded by

raghad mustafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

T esting

Fundamentals
Session 5
Mobile Testing
Deep Dive
Agenda
❖ Major Application Types
❖ Web–based
❖ Native
❖ Hybrid
❖ Mobile Testing Checklist
❖ Build Vs Release
❖ Tips
❖ TestFlight Walkthrough
How Mobile Apps
are Built?
❖ To be able to know how to test it, we should know
how mobile apps are being built.
❖ Now adays mainly there are 3 categorizes:

❖ Web–based apps: when you access a website on


mobile through a browser, here we call it “web
app” or “web-based app” and it’s not a mobile app.
❖ Native: build for a specific mobile operating
system
❖ Hybrid is a mix of native and web-based apps, also
called cross platform apps.
Native VS Hybrid
❖ Built specifically for a mobile operating system such as Apple iOS, Android or ❖ Hybrid apps are built using a single universal language such as JavaScript
Windows phone. which is then able to be exported to various device platforms.
❖ Language code specific and is not interchangeable one with the other. ❖ Most of the code can be shared between platforms
❖ Require a specific development skills related to platform language. ❖ Can be build by same developer for all the platform.
❖ Highly customizable and offer a wide variety of structure and visual appeal. ❖ Limited customization and less variety of structure and visual appeal.
❖ Native apps offer the best user experience as they follow the conventions of ❖ Hybrid apps doesn’t offer the best user experience as they can’t follow
the platform’s user interface (UI) and are faster. the conventions of the platform’s user interface (UI).
❖ Maintenance is typically harder as you need to deal with minimum 2 code ❖ Maintenance is typically easier as you are only dealing with one code base
base to update and maintain. to update and maintain.
❖ More expensive to build than other types of apps, but also offer the most ❖ They are less expensive to build (less development and time)
advantages. ❖ The user experience will be more seamless (unified) between different
❖ The user experience will not be seamless (unified) between different platforms which is important because many people own more than one
platforms. type of device.
How does it effect testing?
❖ Native app testing usually needs more efforts and time.
❖ When testing a hybrid app, many bugs will be applicable to
both platform (iOS, Android) so we should immediately check
and avoid bug duplication.
❖ When testing a native app, probably we will have 2 different
dev teams (developers) where we should be careful in our
bug assignments.
❖ Apply a smart and efficient test execution methodology.
Mobile Testing Checklist
❖ Application installation for the first time
❖ Time to launch the application
❖ Application removal
❖ Application install/uninstall successfully within the desired timeframe
❖ Application behavior upon updating to the new version
❖ Application behavior if there is an incoming call/SMS
❖ Application behavior when the charger is connected/ disconnected
❖ Application behavior when the device goes to sleeping mode
❖ Application behavior when the device resumes from lock screen
❖ Application behavior when the device is tilted (landscape vs portrait)
❖ Application behavior when the device is shaken
❖ Application behavior when switching between the apps
❖ Application behavior when the device is in airplane mode
❖ Application behavior when the device battery is low
Mobile Testing Checklist Cont..
❖ Application interact with the GPS sensor correctly (switch on/off, retrieve GPS data)
❖ Application consistency with the desktop version
❖ Does the app go to sleep mode when running in the background (prevent battery drain)?
❖ Displaying error messages and exits gracefully at times of low memory issues
❖ Does the quick access options work as expected?
❖ Application re-installation behavior
❖ Push notification when application is closed
❖ Push notification when application is opened
❖ Push notification when device is locked
❖ Push notification when device goes to sleeping mode
❖ Can the app be found in the app store? How easy? (Post go-live check)
❖ Is the published version the correct version? (Post go-live check)
Mobile Testing Checklist Samples
Landscape vs Portrait Quick Access Options
Mobile Testing Checklist | Network Specific

❖ Verify the app behavior when connected to the internet through Wi-Fi / 3G / 2G?
❖ Does the app behave according to specification of the app is out of network reach?
❖ Does the app resume working when it gets back into network reach from outside reach of the network?
❖ Update transactions are processed correctly after re-establishing connection.
❖ Does the app still work correctly when tethering or otherwise connected to another device
❖ What happens if the app switches between networks (Wi-Fi, 3G, 2G)
Build Vs Release
❖ “build” is usually given by dev team to the test team while a
“release” is formal release of the product to its customers.
❖ Only when a “build” get tested and certified by the test team
then we can get a form a “release” to production.
❖ Since a “build” can be rejected by test team if any of the tests
fail or it does not meet certain requirements, it’s normally to
that one “release” can have several “builds” associated with it.
Tips Time !
❖ Always ask for the build version and document it
❖ Report crashes even if it’s not reproducible
❖ Location dependency test cases
❖ Compatibility scope and testing is a key
❖ Performance and security testing is very important specially
when the app is open for public, or when we anticipate a
high volume of users.
❖ Localization testing and standard
What is TestFlight?
❖ Apple's TestFlight is a tool created to help
developers distribute their beta apps to users
before they are released on the App Store to
everyone.
❖ Basically, for testing team it’s just an application
we install to be able to download the apps that
need to be tested on iOS.
Walkthrough on TestFlight
Walkthrough on TestFlight
Walkthrough on TestFlight
Walkthrough on TestFlight
Task Time!
Test and log your bugs for the following
applications:
1. Visit Dubai
2. Dubai Calendar
You can download the apps form Apple store or
Google store or from the footer of the website here:
https://www.visitdubai.com/en/

You might also like