I Like to Puppeteer
summary
Company migrates nine-year C# + Selenium suites to JavaScript using Puppeteer, replacing a 100–250MB chromedriver + proxy approach and cutting CI test startup from minutes to about two seconds. Puppeteer intercepts network requests so tests capture and parse Google Analytics pageview and event payloads to assert tracking values, and it runs Chrome/Chromium without an external driver (runs without external driver). Also used for Chrome extension testing and performance timing; cross‑browser support remains limited.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:08Agenda and takeaways
- 4:12Monolith to microservices
- 8:50C# Selenium to JavaScript
- 12:07Why Puppeteer over alternatives
- 13:36Puppeteer setup and test structure
- 15:32Puppeteer demo tracking validation
- 20:17Other Puppeteer use cases
- 22:37Benefits and drawbacks of using Puppeteer
- 24:07Puppeteer in testing scenarios
- 26:42Q&A
related talks
43mPuppeteer Is the New WebDriver? Secrets of Flawless Testing
01h 02mModern web testing and automation with Puppeteer
30mModern Web Testing and Automation with Puppeteer
46mWhen Tests Met Puppeteer
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
51mIs Puppeteer the New WebDriver? Secrets of Flawless Testing
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
01h 15mPuppeteer can automate that!