ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #playwright
Replace manual waits with Playwright locator actionability, expect assertions, and retry configuration to reduce flaky UI tests.
Playwright locator assertions auto-retry until the UI reaches the expected state or the timeout expires. Learn how to configure them and where they do not apply.
Playwright's page.route() intercepts network requests at the browser layer, letting you mock APIs without external dependencies. This post shows a concrete pattern for reliable UI tests, common pitfalls with pattern matching and content-type, and how to verify mocks actually fired using traces.
BrowserStack Local tunnels let cloud browsers reach your localhost or internal staging. Here's how to set it up reliably in CI, handle self-signed certs, and avoid the latency and parallelism traps that bite teams at scale.
Playwright’s browser contexts let you run many isolated E2E tests in parallel without launching a new browser each time. Learn how to create contexts, serialize state, and avoid common pitfalls in this hands‑on guide.
Learn how to choose between Role, Text, and Test-ID locators in Playwright to reduce test flakiness and improve accessibility auditing.
Protractor is deprecated. Learn how to migrate Angular test suites to Playwright or Cypress using a Page Object Model to replace automatic synchronization and Selenium dependencies.
A decision guide for Playwright authentication persistence: use storageState for 90% faster auth reuse across parallel workers, with per-worker files, session validation, and hybrid fallback for multi-role tests. Includes globalSetup implementation, debugging traces, and CI artifact handling.
Use Playwright web-first assertions to wait for dynamic DOM updates automatically instead of adding fixed sleeps that cause flaky end-to-end tests.
browserstack
angular
protractor