That feels quite overwhelming if you are not used to these tools. If you have tried to write tests in Node.js before, you might have come across some weird names: Mocha, Jest, Jasmine, AVA, or Chai. We are going to see the differences between UI Testing and End-to-End testing. In this chapter, we are going to learn the fundamentals of Testing Automation. We learned that Puppeteer is not just about testing, but that doesn't mean that it's not an excellent tool for the job. In this chapter, we are going to cover the second pillar: UI testing. In Chapter 1, Getting started with Puppeteer, we covered the first fundamental pillar of this book: browser automation and headless browsers. 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.īy 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. 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 also get to grips with finding elements using CSS selectors and XPath expressions. You’ll then learn the basics of end-to-end testing and understand how to create reliable tests. 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. 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!
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.
0 kommentar(er)
