Improving Client Side Web Testing Automation in Continuous Integration - A Case Study

Performing testing to improve quality is an important part of the continuous integration process used in many web development organizations. In web development unit testing is done naturally by developers as the first step. After that quality assurance/Automation engineers take over and use tools li...

Full description

Saved in:
Bibliographic Details
Published inProceedings of the International Conference on Software Engineering Research and Practice (SERP) pp. 41 - 47
Main Authors Cox, Sean, Chen, Ning
Format Conference Proceeding
LanguageEnglish
Published Athens The Steering Committee of The World Congress in Computer Science, Computer Engineering and Applied Computing (WorldComp) 01.01.2019
Subjects
Automation
Case studies
Defects
Experiments
Quality assurance
Quality control
Selenium
Software
Software development
Online AccessGet full text

Cover

More Information
Summary:Performing testing to improve quality is an important part of the continuous integration process used in many web development organizations. In web development unit testing is done naturally by developers as the first step. After that quality assurance/Automation engineers take over and use tools like Selenium in order to check the site quality from the user's perspective. Unlike unit testing, performing Selenium tests as a client side automation in a continuous integration process is difficult due to long running cycles and non-deterministic, false negative, results that occurred frequently. To promote and improve the client side automation an experiment was conducted in a web development organization. The results are mixed and expose the needs for a new view on the client side testing role and best practices in a continuous integration process.