{"repo":"percy/percy-puppeteer","free":true,"listed":false,"github":"https://github.com/percy/percy-puppeteer","clone":"git clone https://github.com/percy/percy-puppeteer.git","description":"Visual testing with Puppeteer and Percy","language":"JavaScript","stars":49,"topics":["visual-testing","percy","puppeteer","visual-tests","percy-sdk"],"license":"MIT","category":"scrapers-browser-automation","readme_excerpt":"@percy/puppeteer Percy visual testing for Google Puppeteer. Installation Usage This is an example using the percySnapshot function. For other examples of puppeteer usage, see the Puppeteer docs. Running the code above directly will result in the following logs: When running with percy exec , and your project's PERCY TOKEN , a new Percy build will be created and snapshots will be uploaded to your project. Configuration percySnapshot(page, name[, options]) - page ( required ) - A puppeteer page instance - name ( required ) - The snapshot name; must be unique to each snapshot - options - See per-snapshot configuration options Upgrading Automatically with @percy/migrate We built a tool to help automate migrating to the new CLI toolchain! Migrating can be done by running the following commands and following the prompts: This will automatically run the changes described below for you. Manually Import change In v1.x there wasn't a default export of the package (only a named export). With v2.x the named export is removed and there is only a default export. Migrating Config If you have a previous Percy configuration file, migrate it to the newest version with the config:migrate command:","default_branch":null,"files":null,"tree":[],"storefront":"/r/percy","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/percy/percy-puppeteer/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}