Blog
Puppeteer and headless Chrome: automating CORS regression checks in CI pipelines
Launch headless Chrome with flags matching your users; navigate to pages that trigger cross-origin fetches.
1 min read
puppeteertestingcors
Stable selectors
Wait for network idle after login flows before asserting API calls completed.
Capture HAR exports on failure to compare headers across builds.
Resource limits
Headless browsers are memory heavy; cap concurrent Puppeteer jobs per CI runner.
Reuse browser contexts but isolate cookies between test cases.