Book Image

A Frontend Web Developer’s Guide to Testing

By : Eran Kinsbruner
3 (1)
Book Image

A Frontend Web Developer’s Guide to Testing

3 (1)
By: Eran Kinsbruner

Overview of this book

Testing web applications during a sprint poses a challenge for frontend web app developers, which can be overcome by harnessing the power of new, open source cross-browser test automation frameworks. This book will introduce you to a range of leading, powerful frameworks, such as Selenium, Cypress, Puppeteer, and Playwright, and serve as a guide to leveraging their test coverage capability. You’ll learn essential concepts of web testing and get an overview of the different web automation frameworks in order to integrate them into your frontend development workflow. Throughout the book, you'll explore the unique features of top open source test automation frameworks, as well as their trade-offs, and learn how to set up each of them to create tests that don't break with changes in the app. By the end of this book, you'll not only be able to choose the framework that best suits your project needs but also create your initial JavaScript-based test automation suite. This will enable fast feedback upon code changes and increase test automation reliability. As the open source market for these frameworks evolves, this guide will help you to continuously validate your project needs and adapt to the changes.
Table of Contents (19 chapters)
1
Part 1 – Frontend Web Testing Overview
7
Part 2 – Continuous Testing Strategy for Web Application Developers
11
Part 3 – Frontend JavaScript Web Test Automation Framework Guides

Testing automation evaluation matrix

To realize continuous value from your selected test automation framework, you need to get support for the core elements that you need, as highlighted previously. From language support through to community, advanced testing scenarios support, and testing types of support, those in charge must have a clear picture that they can analyze prior to, as well as during, the adoption and usage of these technologies. The continuous part here is very important, since, for example, as described previously, Cypress currently does not cover iFrames and cannot test WebKit Safari browsers, but these are on their roadmap, so that soon might change. Note that picking your tool stack is good for a given time frame, hopefully long enough, up until you need to re-evaluate your choices and either keep on using what you have or make changes.

In the following table, we will look at the differences and commonalities across the four leading test automation frameworks...