on software testing of mobile application
Now a day’s mobile applications are becoming
so extraordinary, in this field still we unclear about their specific testing
approach for their validation and verification. So we are concentrating in
three aspects which will help us to know about testing functionality and upcoming
challenges , i) Are mobile applications different from traditional apps so to
require different and specialized new testing technique? ii) What are the new
direction and challenges in mobile application testing? Iii)which is the role
automation can play in testing mobile application?
Now a days applications are running in gadgets
(like mobile, tablets, ipad etc.) are becoming
so popular in IT sector. We can see in (mobithinking.com) three years 300,000
mobile applications have been developed & they have been downloaded 10.9
billion times in 2010,29 billion downloads in 2011 & 76.9 billion global
downloads in 2014.In past days mobile was only used for communication and entertainment
but now things are getting change. We are using NFC (Near –Field communication)
and SQUARE (like small credit card reader, which helps millions of run their
business from SOUARE credit card processing to point of sale solution.) both
technology totally changed our payment system.
Mobile application implication on testing
Mobile applications are different from traditional
once so we should investigate how mobile application testing differ from
traditional application testing. So first we should know about mobile
What is mobile application:
A mobile application roughly defined as an
application which taking input as contextual information and running on mobile
device and generate contextual output. Mobile applications classified into two categories:
Traditional application (App4Mobile: which runs on mobile device like searching,
social networking, web navigation) another one is Mobile Application (Mobile
App: that is taking contextual input to generating contextual output).
Future Research Directions and Challenges on Testing
In software testing the main goal is
reducing influence of external factors, maximum fault detection, making result
reproducible. To archive these goals, we can do testing in two ways:
The test process: Research
Directions and Challenges in Test selection and Test Execution in Mobile
§ Test Selection:
Challenges: Test selection process depends on the which
type of application we are testing, if application is context-aware application
so input will vary from place to place. This high variability of inputs leads
to unpredictability on performance of mobile application testing.
Automation and potentials: new benchmark are required to
produce guidelines , strategies and rule by which mobile test cases are
selected to increase coverage of variable contextual and unpredictable inputs.
§ Test Execution:
Challenges: In Mobile application the challenge is how
to execute test cases in rich contextual input.
Automation and potentials: one open source tool is Android Robodium
which enable the automated and black box test execution of third parties
application. For mobile application it resemble selenium.
b)The Test Artefacts: Research Directions
and Challenges in structural and functional testing of mobile applications.
Challenges: we have to add
some extra functionality in mobile application programming for managing mobility,
energy consumption and sensing.
Automation and potentials:
the tool JaBUTi/ME for structural testing approach to execute test cases on
Challenges: For specify
application and environment functional testing is required.
Automation and potentials:
for functional testing of mobile application Monkey Runner tool is required.
Different type of testing strategy
which will help to test more functionality for improving the mobile application
§ Performance and reliability testing:
Challenges: These testing is depends on quality of connectivity,
contextual information, variability.
Automation and potentials: For connectivity
and monitoring resources we can adopt Run-Time analysis technique. One framework
which is invented by Berardinelli et al. for analyzing performance of context
aware mobile system.
§ Memory and Energy Testing:
Challenges: memory leaks can generate limited memory
resource problem and the reason of wastage of energy (Battery) is at a same
time activation of many processes.
Automation and potentials: To generate synthetic
emulation code to estimate power consumption one model driven engineering tool proposed
by Thompson et al.