Automating GUI testing for Android applications

By Cuixiong Hu, Iulian Neamtiu. International Conference/Workshop on Automation of Software Test, 2011

333 citations recorded by the source corpus.

Subfields: Information Systems, Software, Signal Processing

View Paper: https://www.semanticscholar.org/paper/a5372bce78e0c363528e2edbc1a7eb111eefdc44

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

1. Alessandra Gorla
2. Sam Malek
3. Nariman Mirzaei
4. Riyadh Mahmood
5. Mayur Naik
6. Aravind Kumar Machiry
7. Rohan Tahiliani
8. Florian Gross

In Software

1. Alessandra Gorla
2. Sam Malek
3. Nariman Mirzaei
4. Riyadh Mahmood
5. Mayur Naik
6. William Enck
7. Yan Chen
8. Vaibhav Rastogi

In Signal Processing

1. Alessandra Gorla
2. Sam Malek
3. Nariman Mirzaei
4. Riyadh Mahmood
5. Iulian Neamtiu
6. Mayur Naik
7. Aravind Kumar Machiry
8. Rohan Tahiliani

Citations in the corpus

• Using GUI ripping for automated testing of Android applications (2012, result): “D.2.5 [Testing and Debugging]: Testing tools”
• Targeted and depth-first exploration for systematic testing of android apps (2013, background): “Users are increasingly relying on smartphones for computational tasks [1, 2], hence concerns such as app correctness, performance, and security become increasingly pressing [6, 8, 30, 31, 38].”
• Automated Test Input Generation for Android: Are We There Yet? (E) (2015, unknown): “Despite being GUI-based and mainly written in Java, Android apps significantly differ from Java standalone GUI applications and manifest somehow different kinds of bugs [14], [15].”
• Real Challenges in Mobile App Development (2013, background): “Similarly, others [37], [38] are looking into Android apps.”
• AppsPlayground: automatic security analysis of smartphone applications (2013, background): “Hu and Neamtiu [10] have discover GUI bugs in Android applications.”
• What are mobile developers asking about? A large scale study using stack overflow (2015, background): “Fortunately, there is much research currently being done on testing mobile GUIs (i.e., Sadeh et al. 2011; Amalfitano et al. 2011; Hu and Neamtiu 2011).”
• Dynodroid: an input generation system for Android apps (2013, methodology): “Recent work has applied Monkey to find GUI bugs [16] and security bugs [19].”
• EvoDroid: segmented evolutionary testing of Android apps (2014, methodology): “Several recent approaches [18–20, 29, 32, 38] have aimed to improve Android testing practices.”
• A Grey-Box Approach for Automated GUI-Model Generation of Mobile Applications (2013, unknown): “Automated testing of mobile applications: Hu and Neamtiu [23] propose an approach which exercises the app under pseudo-random event sequences produced by the Android Monkey tool and analyzes the log files of this execution for certain kinds of bugs.”
• Checking app behavior against app descriptions (2014, methodology): “Integrating such techniques in CHABADA , combined with automated test generation [12, 27, 15, 1], would allow to learn normal and abnormal patterns of information flow; this is part of our future work (Section 6).”