MobiGUITAR: Automated Model-Based Testing of Mobile Apps

Amalfitano, Domenico; Fasolino, Anna Rita; Tramontana, Porfirio; Ta, Bryan Dzung; Memon, Atif M.

doi:10.1109/ms.2014.55

Cited by 261 publications

(184 citation statements)

References 10 publications

Supporting

Mentioning

172

Contrasting

Unclassified

Order By: Relevance

“…Although they are well-consolidated commercial tools, they do not link test actions with TC descriptions (which is an important link we explore to ease the process of designing and reusing TCs). Moreover, even though we focus our comparison on C&R versus coding approaches for test automation, there are also other well-known strategies such as model-based testing (an example is MobiGUITAR [15]) and GUI ripping (see, for instance, [16]). …”

Section: Doi Reference Number: 1018293/seke2016-228mentioning

confidence: 99%

Capture and Replay with Text-Based Reuse and Framework Agnosticism

Arruda

Sampaio

Barros

2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Software systems need to be constantly tested, either to verify changes or to check conformance to requirements. The current leading approaches to automate GUI tests are coding and the use of Capture & Replay (C&R) tools. Coding is usually associated with (even if ad hoc) reuse strategies, but requires from the developer specialized knowledge about the adopted framework. On the other hand, even though C&R is able to promote faster automation, it raises maintainability and scalability issues in the long term due to scripts scattering and rework for each new test case, because usually there is no associated reuse strategy. In order to combine the benefits of both approaches, we propose: an abstract and framework-free representation of test actions captured during testing activities; a text-based strategy that matches a new test case with previously recorded test actions; and a C&R tool that implements these concepts in the mobile context. We developed and evaluated our strategy in the context of a partnership with Motorola Mobility, achieving a reuse ratio up to 71% with time gains similar to traditional C&R approaches when compared to coding.

show abstract

Section: Doi Reference Number: 1018293/seke2016-228mentioning

confidence: 99%

Capture and Replay with Text-Based Reuse and Framework Agnosticism

Arruda

Sampaio

Barros

2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…Other tools under this category parse applications and automatically generate test cases, e.g., Monkey [8], Android GUITAR [1] and ORBIT [20].…”

Section: Gui Based Testingmentioning

confidence: 99%

A high-level modeling language for the efficient design, implementation, and testing of Android applications

Jaber

Falcone

Dak-Al-Bab

et al. 2016

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

Abstract. Developing mobile applications remains difficult, time consuming, and error-prone, in spite of the number of existing platforms and tools. In this paper, we define MoDroid, a high-level modeling language to ease the development of Android applications. MoDroid allows developing models representing the core of applications. MoDroid provides Android programmers with the following advantages: (1) Models are built using highlevel primitives that abstract away several implementation details; (2) It allows the definition of interfaces between models to automatically compose them; (3) Java native android can be automatically generated along with the required permissions; (4) It supports efficient model-based testing that operates on models. MoDroid is fully implemented and was used to develop several non-trivial Android applications.

show abstract

“…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].…”

Section: Introductionmentioning

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%

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

Self Cite

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

MobiGUITAR: Automated Model-Based Testing of Mobile Apps

Cited by 261 publications

References 10 publications

Capture and Replay with Text-Based Reuse and Framework Agnosticism

Capture and Replay with Text-Based Reuse and Framework Agnosticism

A high-level modeling language for the efficient design, implementation, and testing of Android applications

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

Contact Info

Product

Resources

About