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

Non-functional challenges in web application development

In addition to the challenges mentioned so far, web application developers are also required to continuously guarantee high-performing web applications that are always on and available, as well as an app that 100% adheres to complex accessibility requirements. In this section, we will explore performance and accessibility challenges across web applications.

Performance challenges

For many years, the industry considered a response time of more than 3 seconds for a web application to load (whether running on a desktop browser or a mobile browser) to cause a customer to move to a different website. Research conducted by Limelight Networks, which was featured in an online document published by Broadcom (https://docs.broadcom.com/doc/its-all-about-the-user-experience), shows the different time thresholds and the patience levels of end users today when using web applications. The majority of users will not be willing to wait...