Page 215 - CITS - Electronic Mechanic - TT - 2024
P. 215
ELECTRONICS MECHANIC - CITS
behaviors, performance, and quality of service, as well as features, such as mobility, usability, interoperationability,
connectivity, security, and privacy.”
Related Work in Mobile Application Testing
Many studies address different issues and topics in mobile application testing. Due to space constraints, we
provide a high-level view of recent mobile testing work.
White-box testing
Existing white-box testing methods are still applicable to mobile apps. For example, Java Pathfinder 1 is a mobile
program verification tool supporting white-box mobile Java program testing. Engineers can use this tool to detect
race conditions and deadlocks based on UML state charts and symbolic execution. Riyadh Mahmood and his
colleagues 2 use a whitebox approach to generate test cases with two program-based models (call graph and
architectural) to achieve mobile program code coverage.
Black-box testing
Many black-box testing techniques are useful in mobile app testing. Random testing and the scenario-based
testing method 3 are good examples. GUI-based testing has been discussed in numerous papers. For instance,
Saswat Anand and his colleagues 4 introduced an automated testing approach to validating mobile GUI event
sequences for smartphone apps. Similarly, Domenico Amalfitano and his colleagues 5 presented a tool called
Android Ripper that uses an automated GUI-based technique to test Android apps in a structured manner.
Usability testing
Usability testing helps enhance the quality of the user experience on mobile devices. Anne Kaikkonen her
colleagues6 present a usability testing study and comparative findings in the laboratory as well as in the field.
Quality-of-service testing
The QoS requirements for mobile apps include software performance, reliability, availability, scalability, and
loading speed. Rabeb Mizouni and his colleagues7 evaluated the Web service performance of handheld resource-
constrained clients using SOAP and RESTful technologies. Their focused QoS parameters included response
time, availability, throughput, and scalability.
Wireless connectivity testing
Today, mobile devices support diverse wireless connectivity options, so mobile apps must be validated with
specified wireless connectivity and contexts. Tapani Puhakka and Marko Palola8 addressed this need for B3G
applications and presented an experimental system for automated testing of B3G mobile apps on multiple mobile
phones at the same time. Ichiro Satoh9 presented a new approach, called the flying emulator, to test the software
executed on mobile terminals. Unlike existing approaches, it lets engineers construct emulators as mobile agents
that can travel between computers.
Different mobile test infrastructures:
a emulation,
b cloud,
c device, and
d crowd based.
200
CITS : E & H - Electronics Mechanic - Lesson 127 - 129