EvoDroid: segmented evolutionary testing of Android apps

By Riyadh Mahmood, Nariman Mirzaei, Sam Malek. SIGSOFT FSE, 2014

321 citations recorded by the source corpus.

Subfields: Computer Science Applications, Software, Signal Processing

View Paper: https://www.semanticscholar.org/paper/651bbb1df66bb91f988415925f82101de19d5d1c

How researchers see this paper

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

In Computer Science Applications

1. Yue Jia
2. Mark Harman
3. Ke Mao
4. Koushik Sen
5. George C. Necula
6. Wontae Choi
7. Zhendong Su
8. Yang Liu

In Software

1. Yue Jia
2. Koushik Sen
3. Mark Harman
4. George C. Necula
5. Wontae Choi
6. Ke Mao
7. Zhendong Su
8. Yuting Chen

In Signal Processing

1. Mark Harman
2. Yue Jia
3. Koushik Sen
4. Yuting Chen
5. Ting Su
6. George C. Necula
7. Wontae Choi
8. Zhendong Su

Citations in the corpus

• Guided, stochastic model-based GUI testing of Android apps (2017, methodology): “Evolutionary algo-rithm [40, 41] generates tests by randomly mutating and crossover-ing event sequences to fullfill their optimization goals.”
• Guided GUI testing of android apps with minimal restart and approximate learning (2013, methodology): “EvoDroid [70] is the first Android testing tool based on an evolutionary algorithm.”
• Sapienz: multi-objective automated testing for Android applications (2016, methodology): “CCS Concepts •Software and its engineering → Software testing and debugging; Search-based software engineering; Keywords Android; Test generation; Search-based software testing”
• The Evolution of Android Malware and Android Analysis Techniques (2017, methodology): “…inherently have less code coverage but can use static analysis to guide analyses through more paths [Zheng et al. 2012; Spreitzenbarth et al. 2013; Mahmood et al. 2014] or use apps exercisers like MonkeyRunner, manual input, or intelligent event injectors [Azim and Neamtiu 2013; Machiry et al.…”
• *droid (2016, background): “We refer readers to that work for more information on Android test generation [Amalfitano et al. 2012; Aviv et al. 2012; Xu et al. 2012; Gomez et al. 2013; Machiry et al. 2013; Hao et al. 2014; Liang et al. 2014; Mahmood et al. 2014; Narain et al. 2014].”
• Automated Test Input Generation for Android: Are We There Yet? (E) (2015, unknown): “EvoDroid [19] × × X X × Systematic × White-box”