GUI ripping: reverse engineering of graphical user interfaces for testing
By Atif M. Memon, Ishan Banerjee, Adithya Nagarajan. 10th Working Conference on Reverse Engineering, 2003. WCRE 2003. Proceedings., 2003
439 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/101245256e1a36736045ac9010b0cb5c058ea04f
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
In Information Systems
In Software
Citations in the corpus
- A survey of the use of crowdsourcing in software engineering (2017, methodology): “3) GUI Testing: Automated GUI test case generation is difficult, while manual GUI testing is too slow for many applications [226].”
- Guided, stochastic model-based GUI testing of Android apps (2017, methodology): “Despite much effort [1, 2, 19, 42, 57, 67] in manually or automatically constructing models to represent GUI interactions, MBT’s effectiveness is still limited due to incomplete UI exploration.”
- Using GUI ripping for automated testing of Android applications (2012, result): “Our results show that our GUI-based test cases are able to detect severe, previously unknown, faults in the underlying code, and the structured exploration outperforms a random approach.”
- AppsPlayground: automatic security analysis of smartphone applications (2013, methodology): “We compare our system with GUI Ripper [19].”
- A Grey-Box Approach for Automated GUI-Model Generation of Mobile Applications (2013, methodology): “Comparison of Crawling with and without Action Inference coverage shows our crawler is 32% -75% faster while constructing a 5% -140% more complete model than Android GUITAR and Android GUI Ripper.”