Automated Generation of Oracles for Testing User-Interaction Features of Mobile Apps

Zaeem, Razieh Nokhbeh; Prasad, Munaga V. N. K.; Khurshid, Sarfraz

doi:10.1109/icst.2014.31

Cited by 78 publications

(52 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most of the failures detected by THOR belong to GUI category. The results achieved both by Zaeem et al [15] and Adamsen et al [12] gave us a hint about the relevance of the problem addressed in our paper, since several failures discovered by their techniques were GUI-related and exposed by the orientation change.…”

Section: Testing Apps Through Mobile Specific Eventsmentioning

confidence: 81%

“…The work of Zaeem et al [15] is based on the intuition that different mobile apps and platforms share a set of features referred to as User-Interaction Features and that there is a general, common sense of expectation of how the application should respond to a given feature.…”

Section: Testing Apps Through Mobile Specific Eventsmentioning

confidence: 99%

“…* Unfortunately, the implementation of these recommendations is not straightforward and introduces programming challenges to Android programmers. Several works in the literature have pointed out that many mobile apps actually crash or show failures that can be attributed to orientation change mishandling [4,12,13,14,15].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Why does the orientation change mess up my Android application? From GUI failures to code faults

Amalfitano

Riccio

Paiva

et al. 2017

Software Testing Verif & Rel

View full text Add to dashboard Cite

SummaryThis paper investigates the failures exposed in mobile apps by the mobile-specific event of changing the screen orientation. We focus on GUI failures resulting in unexpected GUI states that should be avoided to improve the apps quality and to ensure better user experience. We propose a classification framework that distinguishes 3 main classes of GUI failures due to orientation changes and exploit it in 2 studies that investigate the impact of such failures in Android apps. The studies involved both open-source and apps from Google Play that were specifically tested exposing them to orientation change events. The results showed that more than 88% of these apps were affected by GUI failures, some classes of GUI failures were more common than others, and some GUI objects were more frequently involved. The app source code analysis allowed us to identify 6 classes of common faults causing specific GUI failures. KEYWORDSAndroid bugs, Android testing, GUI failures, GUI testing, mobile testing, orientation change INTRODUCTIONOver the last decade, the number of users of mobile technology and smartphones has increased considerably. The total number of smartphone users worldwide is forecast to surpass 2.5 billion in 2019 [1].This causes a constant demand for new software applications running on these devices (apps). As of the month of June 2016, both Android and iOS users had the opportunity to choose from among more than 2 million apps [2].Mobile technology has radically changed the lifestyle of billions of people around the world. We use mobile apps for several hours every day, entrust them our sensitive data, and perform a large variety of activities through them, including critical tasks.The demand for app quality has grown together with their spread. Apps users require them to be reliable, robust, efficient, secure, usable, etc.As a consequence, software developers should give proper consideration to the quality of their applications by adopting suitable quality assurance techniques, such as testing.In the last decade, the research community has devoted great interest to the mobile app testing field. Several testing approaches have been proposed to assess different quality aspects of mobile applications [3], such as functionality [4], performance [5], security [6,7], responsiveness [8], and energy consumption [9].Since mobile apps are event-driven systems, many proposed techniques solicit them by means of sequences of events [10]. However, because of the peculiarities of the mobile devices, these apps should be tested with appositely crafted approaches [11]. As an example, testing processes should devote particular attention to exercise the apps through mobile-specific events, such as sending an application to the background and resuming it, receiving a call, changing the state of the network connections, or changing the orientation of the device.Among these types of events, the orientation change deserves special attention. It is a peculiar event in mobile platforms that causes the switch of the running app b...

show abstract

Section: Testing Apps Through Mobile Specific Eventsmentioning

confidence: 81%

Section: Testing Apps Through Mobile Specific Eventsmentioning

confidence: 99%

See 1 more Smart Citation

Why does the orientation change mess up my Android application? From GUI failures to code faults

Amalfitano

Riccio

Paiva

et al. 2017

Software Testing Verif & Rel

View full text Add to dashboard Cite

show abstract

“…This is also witnessed by the growing popularity of MBT in industry [110][111][112][113] and the increasing number of commercial tools available, such as Conformiq Designer [114], Smartesing CertifyIt [115,116] MBT from inferred models MBT from ripped models [32][33][34][35][36][37][38][39] Learningbased MBT [40][41][42][43][44] MBT from finite state models [45][46][47][48][49][50][51][52][53][54] MBT from UML models [55][56][57][58][59] MBT from feature models [60,61] MBT from specification models testing [118]. Recent studies also demonstrated a comparable effort when debugging test cases generated with MBT and manual testing [119].…”

Section: Model-based Testingmentioning

confidence: 99%

Recent Advances in Automatic Black-Box Testing

Mariani

Pezzè

Zuddas

2015

Advances in Computers

View full text Add to dashboard Cite

“…V. RELATED WORK Android bugs have been studied previously for different purposes. For example, Hu and Neamtiu [14] conducted a bug study to investigate the categories of Android bugs and how Android bugs are manifested; Bhattacharya et al [9] performed a bug study to understand the bug-fixing process in Android platform and Android-based apps; and Zaeem et al [21] performed a study to identify user-interaction features for which oracles could be constructed. Different from these studies, our study focuses on investigating bugs that occurred as a result of changes.…”

Section: Rq3: How Does the Number Of Test Cases Selected Bymentioning

confidence: 99%

Redroid: A Regression Test Selection Approach for Android Applications

Dong

Yang

Che

et al. 2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-As the mobile platform pervades human life, much research in recent years has focused on improving the reliability of mobile applications on this platform, for example by applying automatic testing. However, researchers have primarily considered testing of single version of mobile applications. Although regression testing has been extensively studied for desktop applications, and many efficient and effective approaches have been proposed, these approaches cannot be directly applied to mobile applications. We first present a bug study on real-world Android bugs to show the existence of regression bugs, which motivates the need for an efficient regression test selection technique for Android applications. Next, we introduce Redroid, a new approach to regression test selection for Android applications. Our approach leverages the combination of static impact analysis and dynamic code coverage, and identifies a subset of test cases for reexecution on the modified application version. We implement our approach for Android applications, and demonstrate its efficacy through an extensive empirical study.

show abstract

Automated Generation of Oracles for Testing User-Interaction Features of Mobile Apps

Cited by 78 publications

References 20 publications

Why does the orientation change mess up my Android application? From GUI failures to code faults

Why does the orientation change mess up my Android application? From GUI failures to code faults

Recent Advances in Automatic Black-Box Testing

Redroid: A Regression Test Selection Approach for Android Applications

Contact Info

Product

Resources

About