Selenium vs Playwright in 2026: Which One Should QA Engineers Choose?
A head-to-head for 2026 — speed, auto-waiting, language support, ecosystem, and CI stability — to help QA engineers pick the right tool instead of following hype.
Read on Medium →Blog
Practical, no-fluff writing on QA automation — Playwright, Selenium, flaky-test triage, CI/CD stability, and AI-assisted testing with Claude. Need this done for your team? See freelance services →
A head-to-head for 2026 — speed, auto-waiting, language support, ecosystem, and CI stability — to help QA engineers pick the right tool instead of following hype.
Read on Medium →When to reach for Plan Mode, Skills, or Subagents in Claude Code — mapped to real Playwright automation workflows, with the trade-offs of each.
Read on Medium →Using Claude and Playwright MCP to read traces, spot the failing step, and surface root cause automatically — instead of clicking through trace viewers by hand.
Read on Medium →Going from zero iOS automation knowledge to a working suite with only 8 prompts in Cursor — what worked, what broke, and where AI still needs a human.
Read on Medium →How manual testing is shifting toward real-device automation on BrowserStack — running suites across real phones in the cloud without a device lab.
Read on Medium →The real root causes behind flaky Playwright tests — races, auto-waiting misuse, shared state — and a repeatable playbook to make suites deterministic in CI. (Draft — full write-up coming soon.)
Read post →