Automatically repairing broken workflows for evolving GUI applications

Zhang, Sai; Lü, Hao; Ernst, M.

doi:10.1145/2483760.2483775

Cited by 31 publications

(18 citation statements)

References 41 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Two examples include GenProg [20,56], which uses genetic programming to nd viable repairs for C programs, and SPR [23], which uses a staged repair strategy to search through a large space of candidate xes. Alternative analytical approaches also exist, including FixWizard [39], which analyzes bug xes in a piece of code and suggests comparable xes to similar parts of the code base; and FlowFixer [62], which repairs sequences of GUI interactions in modi ed test scripts for Java programs. A group of techniques exists that can detect and repair HTML syntax problems in web applications [38,45].…”

Section: Related Workmentioning

confidence: 99%

Automated repair of layout cross browser issues using search-based techniques

Mahajan

Alameer

McMinn

et al. 2017

Proceedings of the 26th ACM SIGSOFT International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

A consistent cross-browser user experience is crucial for the success of a website. Layout Cross Browser Issues (XBIs) can severely undermine a website's success by causing web pages to render incorrectly in certain browsers, thereby negatively impacting users' impression of the quality and services that the web page delivers. Existing Cross Browser Testing (XBT) techniques can only detect XBIs in websites. Repairing them is, hitherto, a manual task that is labor intensive and requires signi cant expertise. Addressing this concern, our paper proposes a technique for automatically repairing layout XBIs in websites using guided search-based techniques. Our empirical evaluation showed that our approach was able to successfully x 86% of layout XBIs reported for 15 di erent web pages studied, thereby improving their cross-browser consistency. CCS CONCEPTS•So ware and its engineering →So ware testing and debugging; Search-based so ware engineering; KEYWORDSCross-browser issues; automated search-based repair; web apps. ACM Reference format:

show abstract

Section: Related Workmentioning

confidence: 99%

Automated repair of layout cross browser issues using search-based techniques

Mahajan

Alameer

McMinn

et al. 2017

Proceedings of the 26th ACM SIGSOFT International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

show abstract

“…Zhang et al [13] develop a technique to automatically repair broken workflows for evolving GUI applications. They focus on replacement of invalid user interface actions in the original user interface workflows by dynamic profiling, static analysis, and random testing.…”

Section: Related Workmentioning

confidence: 99%

SITAR: GUI Test Script Repair

Gao

Chen

Zou

et al. 2016

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

System testing of a GUI-based application requires that test cases, consisting of sequences of user actions/events, be executed and the software's output be verified. To enable automated re-testing, such test cases are increasingly being coded as low-level test scripts, to be replayed automatically using test harnesses. Whenever the GUI changes-widgets get moved around, windows get merged-some scripts become unusable because they no longer encode valid input sequences. Moreover, because the software's output may have changed, their test oracles-assertions and checkpoints-encoded in the scripts may no longer correctly check the intended GUI objects. We present ScrIpT repAireR (SITAR), a technique to automatically repair unusable low-level test scripts. SITAR uses reverse engineering techniques to create an abstract test for each script, maps it to an annotated event-flow graph (EFG), uses repairing transformations and human input to repair the test, and synthesizes a new "repaired" test script. During this process, SITAR also repairs the reference to the GUI objects used in the checkpoints yielding a final test script that can be executed automatically to validate the revised software. SITAR amortizes the cost of human intervention across multiple scripts by accumulating the human knowledge as annotations on the EFG. An experiment using QTP test scripts suggests that SITAR is effective in that 41-89% unusable test scripts were repaired. Annotations significantly reduced human cost after 20% test scripts had been repaired.

show abstract

“…Precisely, to find the valid selectors, the algorithm first looks for possibly valid elements, represented by PVE (lines [8][9][10][11][12][13][14][15][16][17][18][19][20]. These are the elements that match the original selector up to and including the the selector level c i .level, neglecting the component being assumed erroneous.…”

Section: Analyzing Symptomsmentioning

confidence: 99%

“…In recent work, Zhang et al [20] propose FlowFixer, a technique to repair broken workflows in Java-based GUI applications. Similar to VEJOVIS, FlowFixer attempts to find repairs for errors that arise due to a mismatch between the code and the GUI state.…”

Section: Related Workmentioning

confidence: 99%

Vejovis: suggesting fixes for JavaScript faults

Ocariza

Pattabiraman

Mesbah

2014

Proceedings of the 36th International Conference on Software Engineering

View full text Add to dashboard Cite

JavaScript is used in web applications for achieving rich user interfaces and implementing core functionality. Unfortunately, JavaScript code is known to be prone to faults. In an earlier study, we found that over 65% of such faults are caused by the interaction of JavaScript code with the DOM at runtime (DOM-related faults). In this paper, we first perform an analysis of 190 bug reports to understand fixes commonly applied by programmers to these DOMrelated faults; we observe that parameter replacements and DOM element validations are common fix categories. Based on these findings, we propose an automated technique and tool, called VE-JOVIS, for suggesting repairs for DOM-based JavaScript faults. To evaluate VEJOVIS, we conduct a case study in which we subject VEJOVIS to 22 real-world bugs across 11 applications. We find that VEJOVIS accurately suggests repairs for 20 out of the 22 bugs, and in 13 of the 20 cases, the correct fix was the top ranked one.

show abstract

Automatically repairing broken workflows for evolving GUI applications

Cited by 31 publications

References 41 publications

Automated repair of layout cross browser issues using search-based techniques

Automated repair of layout cross browser issues using search-based techniques

SITAR: GUI Test Script Repair

Vejovis: suggesting fixes for JavaScript faults

Contact Info

Product

Resources

About