tanmay001
Re:
on Monday March 16, 2026 @05:39AM (#47396872)
Playwright's parallelism model has three layers. Most teams configure exactly one and wonder why CI is slow or flaky after bumping workers.
The short version: Layer 1 (file-level) is already running by default. Layer 2 (test-level) is what fullyParallel actually controls, and it's widely misunderstood.
Most teams assume it makes browser projects run simultaneously. It doesn't. It changes the scheduler's unit of work from files to individual tests.
Layer 3 is sharding across machines, which you shouldn't reach for until layers 1 and 2 are properly tuned.
The article covers how workers map to browser processes and why overprovisioning them on low-core CI runners causes the timeouts, what fullyParallel does and doesn't do,per-file execution modes (parallel, serial, default) and how beforeAll behaves differently in each, and three isolation patterns that hold up under parallel runs without needing complex fixture setups. https://testdino.com/blog/playwright-parallel-execution/
Re:Show HN: The Playwright GitHub Repositories Worth Studying
on Thursday March 05, 2026 @02:07AM (#47258509)
Most tutorials teach you the API. Nobody teaches you how to structure a project that doesn't fall apart at 200 tests.
This guide covers 20+ repositories and tools across every category.Official Microsoft repos, TypeScript boilerplates, Python guides, BDD starters, AI skill packs, reporting tools, accessibility plugins, and more. Each one picked for a reason, not just star count.
If your CI is breaking, your config is a mess, or you're just starting out and want to skip the bad patterns early, there's something here for your situation.
Read this full guide with links, setup steps, and a decision framework
Show HN: Playwright CI/CD in GitHub Actions, Jenkins, and GitLab CI
https://testdino.com/blog/best-playwright-ci-cd-integrations/
I wrote a guide on integrating Playwright into the three most common CI systems. It covers what each platform actually requires to run Playwright reliably: browser dependency handling, playwright.config.ts CI settings, parallel sharding, and artifact collection for failed tests. The core issue most teams hit: default CI images don't ship with the system libraries Playwright browsers need (GTK,...
Show HN: Train AI Agents to Write Better Playwright Tests
https://testdino.com/blog/playwright-skill/
AI agents often generate inconsistent Playwright tests because they do not understand your application’s specific workflows, UI patterns, or constraints.The Playwright Skill provides more than 70 structured markdown guides that teach patterns for locators, authentication, visual testing, CI configuration, and framework migration so agents can apply consistent solutions instead of guessing.You...
Show HN: Why Playwright-CLI Beats MCP for AI‑Driven Browser Automation
Most “AI + browser” setups still bolt MCP tools onto Playwright and hope for the best, so every click dumps full DOMs, accessibility trees, and logs into the model.That burns tokens, collapses context, and makes long sessions unreliable.Meanwhile, default Playwright reports start to struggle once you have more than a few dozen e2e tests, so teams drown in HTML reports and flaky failures instead...
Re:Claude Code's DX is too good. And that's a problem
on Tuesday December 16, 2025 @08:08AM (#46288028)
Nice way to put it. Skills feel great for shaping how Claude works inside a repo, while MCP really shines when you want it to talk to “live” systems : databases, test runs, CI, all that external state.