You're reading from A Frontend Web Developer's Guide to Testing Explore leading web test automation frameworks and their future driven by low-code and AI

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781803238319

Length 304 pages

Edition 1st Edition

Languages

JavaScript

Tools

Selenium

Concepts

Front End Web Development

Author (1):

Eran Kinsbruner

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1 – Frontend Web Testing Overview

2. Chapter 1: Cross-Browser Testing Methodologies FREE CHAPTER

3. Chapter 2: Challenges Faced by Frontend Web Application Developers

4. Chapter 3: Top Web Test Automation Frameworks

5. Chapter 4: Matching Personas and Use Cases to Testing Frameworks

6. Chapter 5: Introducing the Leading Frontend Web Development Frameworks

7. Part 2 – Continuous Testing Strategy for Web Application Developers

8. Chapter 6: Map the Pillars of a Dev Testing Strategy for Web Applications

9. Chapter 7: Core Capabilities of the Leading JavaScript Test Automation Frameworks

10. Chapter 8: Measuring Test Coverage of the Web Application

11. Part 3 – Frontend JavaScript Web Test Automation Framework Guides

12. Chapter 9: Working with the Selenium Framework

13. Chapter 10: Working with the Cypress Framework

14. Chapter 11: Working with the Playwright Framework

15. Chapter 12: Working with the Puppeteer Framework

16. Chapter 13: Complementing Code-Based Testing with Low-Code Test Automation

17. Chapter 14: Wrapping Up

18. Other Books You May Enjoy

Packt is searching for authors like you

A re-evaluation of test automation frameworks due to compelling events

Comparing all the preceding capabilities is a great way to perform due diligence across the leading test automation frameworks on the market; however, such a comparison is a timely activity that must be done multiple times.

The market and the web application project life cycle often trigger a need to change the framework that's being used by frontend developers and SDETs. The following are a few examples of such compelling events:

A new web application developed from scratch: Within a web project life cycle, the product management team or the business as a whole may decide that it's time for a full refresh of a website. With such a refresh, developers might pick a new development framework, as well as decide that the web application will be of the PWA type. A new project has a new UI, new requirements, new business flows, and so on. That's a valid trigger to re-assess the test automation...