Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Selecting the Right Mobile Test Automation Strategy: Challe

No description

adi stein

on 12 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Selecting the Right Mobile Test Automation Strategy: Challe

Selecting the Right Mobile Test Automation Strategy: Challenges and Principles
Problems and Challenges in Mobile Application Test Automation
Main mobile apps test mechanism
Mobile Test Automation Types
Key Principles in Selecting the Right Tools for Mobile Testing
Market tools and short demo
Native VS Web Mobile Applications
What's the problem?
Multiple platforms and browsers (with Rendering differences.)
Compare weighting table
Manual Testing
on all possible work flows including: all fields , all combination, all rainy scenarios implies time and cost consuming

Automation Testing
does not require Human intervention
Automation increases  speed of test execution

Manual Testing can become tedious and hence error prone

Test Automation Mechanisms
User agent-based automation
Add-ons that come with popular browsers such as Mozilla Firefox and Google Chrome
Lab-based automation
test environment and leveraging simulators or physical devices to automate testing using popular open-source tools such as selenium.
QTP, Selenium or RFT
Optimal Testing Strategy: This table compares these variables and the optimal test strategy for each type of testing
Key Principles in Selecting the Right Tools for
Mobile Testing
Many different devices
Large fragmentation of OS
Perform tool
feasibility tests
, because mobile technologies and platforms vary.
Select tools that
support both platform simulators and devices
, because you can mix and match devices and simulators to optimize runs on different platforms.
device support and versions support.
on platform support: In some cases, there may be a need for one or
more tools
to perform automation.
Aim for automation in nonfunctional areas —
interruption and hardware scenarios that include battery state changes.
Determine the use of utilities and
reusable functions
that add value to automation.
per each mobile platform and duration of execution as part of the
tool consideration process
Look for avenues for

, because most mobile projects are Agile.
Integrated execution with the
test management tool
and application
life cycle management
is an important success factor for a tool.
QA Automation Tools
Good candidates for automation are test cases that have r
epeated business logic, functional flows
or data-driven tests: Smoke test and build acceptance testing, regression testing, synchronization testing, compatibility testing, GUI testing and testing non-dynamic UI components, as well as cross-platform functional testing.
Champions' tips-
Proof of concept
Identify reusable scenarios across platforms and group them accordingly
For native apps- choose critical test cases that can
be run across releases as automation candidates
and ensure that there is a cross-platform reusability
and multi-browser compatibility.
Automation Soft Demo
Selecting the Right Mobile Test Automation Strategy: Challenges and Principles
Differences in Testing
Test App installation
No installation needed
Native Apps
Mobile Web
Special considerations:
cognizant, Pradeep Kumar Govindasamy
Native Apps vs. Mobile Web vs. Hybrid Apps
Check API access
Custom Themes
Screen Size
(3 sec rule)
Load time very importent
Requires internet connection
Browsers rendering differences
Problems and Challenges in Mobile Application Test Automation
Main mobile apps test mechanism
Mobile Test Automation Types
Key Principles in Selecting the Right Tools for Mobile Testing
Market tools and short demo
Native VS Web Mobile Applications
Mobile phone use has been growing exponentially

The Smartphone Boom
What's the problem?
Network Challenges
Multiple platforms and browsers (with Rendering differences.)
Transition from “just a phone” to a multipurpose gadget

The Smartphone Boom
Many different devices
Large fragmentation of OS
Multiple network types (e.g., GSM/GPRS/Wi-Fi/Wi-Max)

Different speeds of connectivity across (chaeta vs snail) geographies
Multiple network operators with customized network features
Hardware Challenges
Limitations in processing speed.
Limitations of mobile memory size. (GB vs.) TB

Differences in device communication protocols
(e.g., WAP/HTTP).
Sample Test Execution
Test execution across different devices and browsers is a huge

Designing a test execution matrix is both difficult and time-consuming
Agile development vs. Device Diversity
(No more waterfall development days. )
Fast paced reality demands agile development
(On the other hand ) - But mobile applications must be tested
(to ensure they run in a satisfying manner )
(what will happen if there won’t be QA?)

Why Failing Hurts
(In the past one’s bad UX speeded slowly via word of mouth)

It's all about the money
ROI POV – the earlier bugs are located - the better
A bad review could mean black stamp on the app
60% of mobile users will abandon your app or site if it doesn’t load within 3 seconds
Can’t be deleted
Performance concerns (Memory, battery)
Network Challenges
Hardware Challenges
common mobile Issues
Functional Testing
Sign-up & Login
Menu Options
Does your mobile app store saved information properly? What about data deletion – or worse – unintended data deletion?
Connection Speed / Carrier
Operating System
Screen Size
battery is at full strength, medium strength and low strength? / incoming calls, SMS, MMS and video calls.
Error Messages
performance testing of applications is
mobile system resources are limited
Data Handling
does the app perform its functions as intended?
is intuitive? fit familiar look of other mobile apps? meet the requirement of the vendor? (apple)
need to be done by USERS (beta/ UAT)
comment. will be removed
At the base the, Unit Tests, there are lots and lots of tests and they typically execute in milliseconds. I typically hear people say there are between two and four times as much test code (for unit tests) as production code.
Cost is proportional to time - and manual testing is an order of magnitude more expensive than automated tests over anything other than the very short run - and therefore as tests take longer to run costs go up.
As you rise up there are fewer tests, tests take longer to execute and therefore tend to be run less often. Also as you rise up it becomes more difficult to automate the tests, you can automate but it requires more effort and more co-ordination. Therefore manual testing continues to exist.
tools such as Perfecto
Mobile and Device Anywhere.
Cloud-based automation
The mobile testing process is not suited to a one-size-fits-all approach.
You have different goals that require different types and levels of testing at different stages in the process. These needs dictate whether it makes sense to test manually or to automate your testing.
Should I use manual or automated tests?
comment- will be deleted
http://qa.blogix.co.il/2012/06/10/ (testing stategies)
(page 26)
Special thank you to Asaf Saar
(Tenkod) for his assistance
watch?v=dlBX7FE5ApA @youtube.com (Sikuly tutorial)
Full transcript