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

Leotta, Maurizio; Stocco, Andrea; Ricca, Filippo; Tonella, Paolo

doi:10.1145/2695664.2695847

Cited by 19 publications

(18 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Starting from the preliminary prototype of P esto , which was implemented in the context of our previous work , we decided to extend P esto based on the limitations observed during migration of existing DOM‐based test suites to the visual approach. Thus, we searched for existing test suites that could be used to guide the development and improvement of P esto .…”

Section: Pesto Improvement Processmentioning

confidence: 99%

“…After the development of the training test suites, we tried to migrate them to the visual approach by means of the preliminary version of P esto (see Figure ).…”

Section: Pesto Improvement Processmentioning

confidence: 99%

“…This paper is a substantially revised version of our original proposal presented in conference and tool demo papers. The main extensions are as follows: we improved P esto to support a more complete set of Selenium WebDriver commands.…”

Section: Introductionmentioning

confidence: 99%

“…The previous version of P esto supported only click(), sendKeys(), and getText(); we improved P esto with multi‐state locators, in order to manage the interaction with Web elements that change their visual rendering during the execution of the test suite (eg, a check box that can be checked or un‐checked); we performed a more thorough evaluation of P esto , on an extended set of test cases. In our previous work , we used four DOM‐based test suites composed of 68 test cases and 213 Web elements (2556 Java lines of code [LOCs] overall for the DOM‐based test suites). In this work, we enhanced the same four test suites and increased by 140% the number of test cases (163) and by 152% the number of Web elements (537), resulting in 5626 Java LOCs for the DOM‐based test suites.…”

Section: Introductionmentioning

confidence: 99%

“…In particular, we added the support for the following:selectByVisibleText(), selectByIndex(), and clear(). The previous version of PESTO [10,11] supported only click(), sendKeys(), and getText();• we improved PESTO with multi-state locators, in order to manage the interaction with Web elements that change their visual rendering during the execution of the test suite (eg, a check box that can be checked or un-checked);• we performed a more thorough evaluation of PESTO, on an extended set of test cases. In our previous work [10], we used four DOM-based test suites composed of 68 test cases and 213 Web elements (2556 Java lines of code [LOCs] overall for the DOM-based test suites).…”

mentioning

confidence: 99%

See 4 more Smart Citations

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

Leotta

Stocco

Ricca

et al. 2018

Software Testing Verif & Rel

Self Cite

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

Section: Pesto Improvement Processmentioning

confidence: 99%

“…After the development of the training test suites, we tried to migrate them to the visual approach by means of the preliminary version of P esto (see Figure ).…”

Section: Pesto Improvement Processmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

mentioning

confidence: 99%

See 3 more Smart Citations

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

Leotta

Stocco

Ricca

et al. 2018

Software Testing Verif & Rel

Self Cite

View full text Add to dashboard Cite

show abstract

Robula+: an algorithm for generating robust XPath locators for web testing

Leotta

Stocco

Ricca

et al. 2016

J. Softw. Evol. and Proc.

Self Cite

View full text Add to dashboard Cite

Automated test scripts are used with success in many web development projects, so as to automatically verify key functionalities of the web application under test, reveal possible regressions and run a large number of tests in short time. However, the adoption of automated web testing brings advantages but also novel problems, among which the test code fragility problem. During the evolution of the web application, existing test code may easily break and testers have to correct it. In the context of automated DOM-based web testing, one of the major costs for evolving the test code is the manual effort necessary to repair broken web page element locators -lines of source code identifying the web elements (e.g. form fields and buttons) to interact with.In this work, we present ROBULA+, a novel algorithm able to generate robust XPath-based locatorslocators that are likely to work correctly on new releases of the web application. We compared ROBULA+ with several state of the practice/art XPath locator generator tools/algorithms. Results show that XPath locators produced by ROBULA+ are by far the most robust. Indeed, ROBULA+ reduces the locators' fragility on average by 90% w.r.t. absolute locators and by 63% w.r.t. Selenium IDE locators.

show abstract

Automatic monitoring of service reliability for web applications: a simulation‐based approach

Kim

Suh

Chung

2020

Software Testing Verif & Rel

View full text Add to dashboard Cite

SummaryWith the recent development of Internet technologies, various web browser‐based applications and services, such as Google and Facebook, are provided. Although many web applications and services make life more efficient for users, they may become unavailable for various reasons. This can have substantial negative impacts on both users and service providers. 24/7/365 web services are especially critical in enterprise environments for establishing their business continuity. For this reason, real‐time service monitoring is the most vital factor for web application providers. Various methods to monitor web applications reliability have been proposed over the past years. However, existing approaches concentrate more on functional testing rather than considering the users perspective. Also, they cannot monitor web applications that rely on web browser application programming interfaces (APIs) or client programmes. In this paper, we propose a novel approach called SAM, which can pinpoint web application failures, including those that require browser APIs or client programmes. We describe the implementation of the SAM system and present the results of an empirical evaluation of a real‐world web application

show abstract

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

Cited by 19 publications

References 12 publications

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

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

Robula+: an algorithm for generating robust XPath locators for web testing

Automatic monitoring of service reliability for web applications: a simulation‐based approach

Contact Info

Product

Resources

About