A test case refactoring approach for pattern-based software development

Chu, Pei Ming; Hsueh, Nien-Lin; Chen, Hong-Hsiang; Liu, Chien-Hung

doi:10.1007/s11219-011-9143-x

Cited by 14 publications

(6 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our tool is developed on top of Spoon, a Java library for source code transformation and analysis. 6 B-Refactoring handles a number of interesting cases and uses its own test driver to take them into account.…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Dynamic Analysis can be Improved with Automatic Test Suite Refactoring

Xuan,

Cornu,

Martinez

et al. 2015

Preprint

View full text Add to dashboard Cite

Context:Developers design test suites to automatically verify that software meets its expected behaviors. Many dynamic analysis techniques are performed on the exploitation of execution traces from test cases. However, in practice, there is only one trace that results from the execution of one manually-written test case. Objective:In this paper, we propose a new technique of test suite refactoring, called B-Refactoring. The idea behind B-Refactoring is to split a test case into small test fragments, which cover a simpler part of the control flow to provide better support for dynamic analysis. Method:For a given dynamic analysis technique, our test suite refactoring approach monitors the execution of test cases and identifies small test cases without loss of the test ability. We apply B-Refactoring to assist two existing analysis tasks: automatic repair of if-condition bugs and automatic analysis of exception contracts. Results:Experimental results show that test suite refactoring can effectively simplify the execution traces of the test suite. Three real-world bugs that could previously not be fixed with the original test suite are fixed after applying B-Refactoring; meanwhile, exception contracts are better verified via applying B-Refactoring to original test suites. Conclusions:We conclude that applying B-Refactoring can effectively improve the purity of test cases. Existing dynamic analysis tasks can be enhanced by test suite refactoring.

show abstract

Section: Methodsmentioning

confidence: 99%

“…Test case refactoring aims to rearrange test cases according to a certain task [37], [24], [6]. Test case purification is a type of test case refactoring that aims to minimize the number of impure test cases.…”

Section: ) Test Case Purificationmentioning

confidence: 99%

Dynamic Analysis can be Improved with Automatic Test Suite Refactoring

Xuan,

Cornu,

Martinez

et al. 2015

Preprint

View full text Add to dashboard Cite

show abstract

“…Chu et al proposed a plugin tool to guide test case refactoring after having applied well‐established pattern‐based code refactoring. While refactoring the application, using a series of patterns, their plugin records all the useful steps and information.…”

Section: Related Workmentioning

confidence: 99%

“…Most of Fowler's refactorings require explicit actions to keep the interface between test and application code compatible. Thus, they propose the notion of test-first refactoring, which modifies the existing test cases so as to obtain an executable starting point for the application code level refactoring.Chu et al[59] proposed a plugin tool to guide test case refactoring after having applied well-established pattern-based code refactoring. While refactoring the application, using a series of patterns, their plugin records all the useful steps and information.…”

mentioning

confidence: 99%

Pesto: Automated migration of DOM‐based Web tests towards the visual approach

Leotta

Stocco

Ricca

et al. 2018

Software Testing Verif & Rel

View full text Add to dashboard Cite

Summary Test automation tools are widely adopted for testing complex Web applications. Three generations of tools exist: first, based on screen coordinates; second, based on DOM–based commands; and third, based on visual image recognition. In our previous work, we proposed Pesto, a tool able to migrate second‐generation Selenium WebDriver test suites towards third‐generation Sikuli ones. In this work, we extend Pesto to manage Web elements having (1) complex visual interactions and (2) multiple visual appearances. Pesto relies on aspect‐oriented programming, computer vision, and code transformations. Our new improved tool has been evaluated on two Web test suites developed by an independent tester. Experimental results show that Pesto manages and transforms correctly test suites with Web elements having complex visual interactions and multistate elements. By using Pesto, the migration of existing DOM–based test suites to the visual approach requires a low manual effort, since our approach proved to be very accurate.

show abstract

“…TTtwo2three has been used to convert two industrial test suites, a Bluetooth Serial Port Profile and a UMTS network element, consisting of about 2,500 test cases. Chu et al [5] propose a tool to guide test case refactoring after having applied well-established pattern-based code refactoring. While refactoring the application, using a series of patterns, the plugin records all the useful steps and information.…”

Section: Related Workmentioning

confidence: 99%

Automated generation of visual web tests from DOM-based web tests

Leotta

Stocco

Ricca

et al. 2015

Proceedings of the 30th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Functional test automation is increasingly adopted by web applications developers. In particular, 2nd generation tools overcome the limitations of 1st generation tools, based on screen coordinates, by providing APIs for easy selection and interaction with Document Object Model (DOM) elements. On the other hand, a new, 3rd generation of web testing tools, based on visual image recognition, brings the promise of wider applicability and simplicity. In this paper, we consider the problem of the automated creation of 3rd generation visual web tests from 2nd generation test suites. This transformation affects mostly the way in which test cases locate web page elements to interact with or to assert the expected test case outcome. Our tool PESTO determines automatically the screen position of a web element located in the DOM by a DOM-based test case. It then determines a rectangle image centred around the web element so as to ensure unique visual matching. Based on such automatically extracted images, the original, 2nd generation test suite is rewritten into a 3rd generation, visual test suite. Experimental results show that our approach is accurate, hence potentially saving substantial human effort in the creation of visual web tests from DOM-based ones

show abstract

A test case refactoring approach for pattern-based software development

Cited by 14 publications

References 18 publications

Dynamic Analysis can be Improved with Automatic Test Suite Refactoring

Dynamic Analysis can be Improved with Automatic Test Suite Refactoring

Pesto: Automated migration of DOM‐based Web tests towards the visual approach

Automated generation of visual web tests from DOM-based web tests

Contact Info

Product

Resources

About