Book Image

UI Testing with Puppeteer

By : Dario Kondratiuk
Book Image

UI Testing with Puppeteer

By: Dario Kondratiuk

Overview of this book

Puppeteer is an open source web automation library created by Google to perform tasks such as end-to-end testing, performance monitoring, and task automation with ease. Using real-world use cases, this book will take you on a pragmatic journey, helping you to learn Puppeteer and implement best practices to take your automation code to the next level! Starting with an introduction to headless browsers, this book will take you through the foundations of browser automation, showing you how far you can get using Puppeteer to automate Google Chrome and Mozilla Firefox. You’ll then learn the basics of end-to-end testing and understand how to create reliable tests. You’ll also get to grips with finding elements using CSS selectors and XPath expressions. As you progress through the chapters, the focus shifts to more advanced browser automation topics such as executing JavaScript code inside the browser. You’ll learn various use cases of Puppeteer, such as mobile devices or network speed testing, gauging your site’s performance, and using Puppeteer as a web scraping tool. By the end of this UI testing book, you’ll have learned how to make the most of Puppeteer’s API and be able to apply it in your real-world projects.
Table of Contents (12 chapters)

Exposing local functions

With Puppeteer, you can not only execute code inside the browser but also make calls from the browser back to your Node app. The exposeFunction function allows us to register Node functions inside the browser.

This is the exposeFunction signature: page.exposeFunction(name, puppeteerFunction):

  • The first argument is name. This will be the function name inside the browser.
  • puppeteerFunction is a function that follows the same style and functionality as all the functions we have learned about in this chapter.

This feature is perfect when it is called from a MutationObserver.

For instance, instead of executing a function over and over, waiting for the checkout counter to change, we could create a MutationObserver to let us know when the value has changed in the HTML Node. Let's see how the code would look:

let observer = new MutationObserver(list => console.log(list[0].target.nodeValue));
observer.observe(
  document...