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

Compliance challenges for web applications

Data privacy and cyber security have grown to become two of the biggest challenges and concerns for web and mobile application developers. Failing to protect a web application from significant data breaches and other vulnerabilities can mean the difference between a living business and a failing one. Since security and data privacy is a 24/7 risk, web application developers must build security early into the functionality of their apps, leverage Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST) tools, and maintain their code continuously.

SAST

SAST is a method for inspecting and analyzing application source code, byte code, and binaries for coding and design conditions to determine security vulnerabilities. Unlike DAST, SAST is also known as a white box testing approach that scans the source code of the application in a non-running state.

DAST

DAST is a method that is also known as black...