In the newly opened test browser, type F8 to resume test execution In Chrome open chrome://inspect/#devices and click inspect Run node -inspect-brk, eg node -inspect-brk node_modules/.bin/jest tests Give it a spin: Getting Started Installationĭebugger await page. Capture a timeline trace of your site to help diagnose performance issues.Run your tests directly in the latest version of Chrome using the latest JavaScript and browser features. Create an up-to-date, automated testing environment.Automate form submission, UI testing, keyboard input, etc.Crawl a SPA (Single-Page Application) and generate pre-rendered content (i.e.Generate screenshots and PDFs of pages.Most things that you can do manually in the browser can be done using Puppeteer! Here are a few examples to get you started: Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium. Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol.
Package.json "devDependencies": "^7.3.API | FAQ | Contributing | Troubleshooting
I have searched around and found others with this problem, but no solid ways around this. When I do initial npm i I see > install /Users/./node_modules/puppeteerĭownloading Chromium r549031 - 76 Mb 100% 0.0sĬhromium downloaded to /Users/./node_modules/puppeteer/.local-chromium/mac-549031īut this doesn't work and I get the revision error.Īfter I node install.js in Puppeteer's dir, I see Downloading Chromium r637110 - 85.9 Mb 100% 0.0sĬhromium downloaded to /Users/./node_modules/puppeteer/.local-chromium/mac-637110Īny ideas why? This is on macOS & Node 10.15 and I assume it's going to be more difficult to do this in CI. It would seem that npm i with Puppeteer in my deps would be enough, but after install completes, I need to cd into /node_modules/puppeteer then run node install.js to get the correct revision downloaded. Otherwise, when I try to run tests using Puppeteer, I get Error: Chromium revision is not downloaded.
0 kommentar(er)
