Visual vs. DOM-Based Web Locators: An Empirical Study

Leotta, Maurizio; Clerissi, Diego; Ricca, Filippo; Tonella, Paolo

doi:10.1007/978-3-319-08245-5_19

Cited by 52 publications

(45 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Maintenance costs that are discussed theoretically and presented through qualitative observations from industrial projects (Karhu et al 2009;Berner et al 2005). Some empirical research on maintenance costs have been reported but for open source software (Leotta et al 2013(Leotta et al , 2014Nguyen et al 2014) whilst the number of papers that include industrial systems are limited (Sjösten-Andersson and Pareto 2006).…”

Section: Related Workmentioning

confidence: 99%

On the long-term use of visual gui testing in industrial practice: a case study

Alégroth

Feldt

2017

Empir Software Eng

View full text Add to dashboard Cite

Visual GUI Testing (VGT) is a tool-driven technique for automated GUI-based testing that uses image recognition to interact with and assert the correctness of the behavior of a system through its GUI as it is shown to the user. The technique's applicability, e.g. defect-finding ability, and feasibility, e.g. time to positive return on investment, have been shown through empirical studies in industrial practice. However, there is a lack of studies that evaluate the usefulness and challenges associated with VGT when used long-term (years) in industrial practice. This paper evaluates how VGT was adopted, applied and why it was abandoned at the music streaming application development company, Spotify, after several years of use. A qualitative study with two workshops and five well chosen employees is performed at the company, supported by a survey, which is analyzed with a grounded theory approach to answer the study's three research questions. The interviews provide insights into the challenges, problems and limitations, but also benefits, that Spotify experienced during the adoption and use of VGT. However, due to the technique's drawbacks, VGT has been abandoned for a new technique/framework, simply called the Test interface. The Test interface is considered more robust and flexible for Spotify's needs but has several drawbacks, including that it does not test the actual GUI as shown to the user like VGT does. From the study's results it is concluded that VGT can be used long-term in industrial practice but it requires organizational change as well as engineering best practices to be beneficial. Through synthesis of the study's results, and results from previous work, a set of guidelines are presented that aim to aid practitioners to adopt and use VGT in industrial practice. However, due to the abandonment of the technique, future research is required to analyze in what types of projects the technique is, and is not, long-term viable. To this end, we also present Spotify's Test interface solution for automated GUI-based testing and conclude that it has its own benefits and drawbacks.

show abstract

Section: Related Workmentioning

confidence: 99%

On the long-term use of visual gui testing in industrial practice: a case study

Alégroth

Feldt

2017

Empir Software Eng

View full text Add to dashboard Cite

show abstract

“…These approaches offer different payoffs in terms of maintenance [Leotta et al 2014]. Location maintenance is addressed through both preventive and curative approaches (see Grace et al [2011] for an overview).…”

Section: Maintainabilitymentioning

confidence: 99%

The Augmented Web

Díaz

Arellano

2015

ACM Trans. Web

View full text Add to dashboard Cite

Today's web personalization technologies use approaches like user categorization, configuration, and customization but do not fully support individualized requirements. As a significant portion of our social and working interactions are migrating to the web, we can expect an increase in these kinds of minority requirements. Browser-side transcoding holds the promise of facilitating this aim by opening personalization to third parties through web augmentation (WA), realized in terms of extensions and userscripts. WA is to the web what augmented reality is to the physical world: to layer relevant content/layout/navigation over the existing web to improve the user experience. From this perspective, WA is not as powerful as web personalization since its scope is limited to the surface of the web. However, it permits this surface to be tuned by developers other than the sites' webmasters. This opens up the web to third parties who might come up with imaginative ways of adapting the web surface for their own purposes. Its success is backed up by millions of downloads. This work looks at this phenomenon, delving into the "what," the "why," and the "what for" of WA, and surveys the challenges ahead for WA to thrive. To this end, we appraise the most downloaded 45 WA extensions for Mozilla Firefox and Google Chrome as well as conduct a systematic literature review to identify what quality issues received the most attention in the literature. The aim is to raise awareness about WA as a key enabler of the personal web and point out research directions.

show abstract

“…These auto-generated keywords will be used later by the automation framework to test the SUT. The main issue in this solution is that output test steps from the English written test cases are not 100% guaranteed to be correct because the user can express a test case in many different forms [36]. This requires human intervention to revise the auto-generated steps before running them.…”

Section: Fig 4 Hybrid Testing Frameworkmentioning

confidence: 99%

Automated Software Testing Frameworks: A Review

Hanna¹,

Elsayed²,

Mostafa-Sami³

2018

IJCA

View full text Add to dashboard Cite

Manual software testing has been traditionally used in the software industry. It depends completely on human testers without the help of any tool to detect the unexpected behavior of an application. However, the main problem in the manual testing approach is that it is a time-consuming task in addition to the fact that tests cannot be reused. Automation software testing has been introduced to reduce testing efforts and detect as many faults as possible. Test cases are executed not only to test the functional requirements for the first time, but also to check the functions which have been already tested. This study aims to present the main features of different automation testing frameworks. In addition, an overview of different scripting techniques is presented during the study.

show abstract

Visual vs. DOM-Based Web Locators: An Empirical Study

Cited by 52 publications

References 16 publications

On the long-term use of visual gui testing in industrial practice: a case study

On the long-term use of visual gui testing in industrial practice: a case study

The Augmented Web

Automated Software Testing Frameworks: A Review

Contact Info

Product

Resources

About