Impact of Execution Modes on Finding Android Failures | Zendy

Inês Coimbra Morgado | Zendy; Ana C. R. Paiva | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

Impact of Execution Modes on Finding Android Failures

Author(s) -

Inês Coimbra Morgado,

Ana C. R. Paiva

Publication year - 2016

Publication title -

procedia computer science

Language(s) - English

Resource type - Journals

SCImago Journal Rank - 0.334

H-Index - 76

ISSN - 1877-0509

DOI - 10.1016/j.procs.2016.04.127

Subject(s) - computer science , android (operating system) , graphical user interface testing , automation , android application , mobile device , user interface , test case , embedded system , human–computer interaction , operating system , user interface design , machine learning , mechanical engineering , engineering , regression analysis

The iMPAcT tool combines the benefits of existing user recurring behaviour (User Interface Patterns) on mobile applications to facilitate the test automation of Android mobile applications. It uses an automatic exploration process combined with reverse engineering to identify the existing user interface patterns on a mobile application and then tests those patterns with generic test strategies (designated Test Patterns). The Test Patterns are defined in a catalogue that can be reused for testing other applications. However the results obtained by the iMPAcT tool depend on the exploration mode and on the order in which the test strategies are applied. This paper describes an experiment conducted to evaluate the impact of using different exploration modes and of changing the order by which UI patterns are searched and subsequently tested on the failures found and on the number of events fired

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research