Example: navigating to and saving a screenshot as example. You create an instance of Browser, open pages, and then manipulate them with Puppeteer's API.
Puppeteer will be familiar to people using other browser testing frameworks. Puppeteer uses several defaults that can be customized through configurationįor example, to change the default cache directory Puppeteer uses to installīrowsers, you can add a. All examples below use async/await which is only supported in Node v7.6.0 or greater. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see
Your project folder (see an example below) because not all hosting providers Heroku, you might need to reconfigure the location of the cache to be within If you deploy a project using Puppeteer to a hosting provider, such as Render or Puppeteer is very useful for several task types on the web (crawling, testing, debugging, scrapping, automation. verifyswcaching.js Verify all the resources you expect are being cached by a service worker for offline.
Output from some of the examples: codecoverage.js Test lazy loading strategy by seeing CSS/JS code coverage usage across page load. The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). Examples for using Puppeteer to do big, bold things. When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to
0 kommentar(er)
