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

Summary

In this chapter, we explored the different but important capabilities of a test automation framework and dived deeper into how each of the four leading test automation frameworks supports and works to address these capabilities. There is no clear-cut choice of framework, since a web application project is very complex and has different requirements and testing criteria.

This chapter gave some guidance in terms of each capability about whether a test framework can accomplish more, or if it's easier to use one compared to another. We have seen examples of capabilities that are built into the test frameworks as opposed to those that require an external plugin to be installed (such as XPath support).

As a frontend developer and/or SDET, you can use this chapter to create your own tailored consideration matrix that will fit your project. If your project requires more in-depth visual testing, performance testing, and network control, you can clearly see which of the...