Pushing the limits on automation in GUI regression testing
Authors:
- 1 November 2015
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 565-575
Abstract
Although there has been much work on automated GUI regression testing of software, full automation continues to etude us. There are two significant impediments to full automation: obtaining (J) test inputs and (2) test oracle. We now push the envelope 011 full automation of GUI regression testing by fully automatically generating test cases as well as the test oracle, completely eliminating manual work. This allows us to study issues of false positives/negatives in test failure; we provide ways to minimize these. The results of our empirical studies suggest that our approach of using workflow-based test eases, derived front the software under test, may help empower the end user to perform regression testing before applying software updates.Keywords
This publication has 25 references indexed in Scilit:
- Making System User Interactive Tests Repeatable: When and What Should We Control?2015
- Regression testing minimization, selection and prioritization: a surveySoftware Testing, Verification and Reliability, 2012
- Designing and comparing automated test oracles for GUI-based software applicationsACM Transactions on Software Engineering and Methodology, 2007
- Selective capture and replay of program executionsACM SIGSOFT Software Engineering Notes, 2005
- GUI ripping: reverse engineering of graphical user interfaces for testing2004
- Regression testing of GUIs2003
- Testing2000
- Certifying off-the-shelf software componentsComputer, 1998
- Generating oracles from your favorite temporal logic specificationsACM SIGSOFT Software Engineering Notes, 1996
- TAOS: Testing with Analysis and Oracle Support1994