Playwright 1.59.1 Released — What’s New for QA Engineers

What’s New in Playwright 1.59.1

Playwright version 1.59.1 was released on April 01, 2026.
Here is a summary of what changed and what it means for QA engineers and SDETs.

Official Release Notes

### Bug Fixes

- **[Windows]** Reverted hiding console window when spawning browser processes, which caused regressions including broken `codegen`, `--ui` and `show` commands ([#39990](https://github.com/microsoft/playwright/issues/39990))

How to Upgrade

# For Python tools
pip install playwright --upgrade

# For Node.js tools  
npm install playwright@latest

Full release notes: https://github.com/microsoft/playwright/releases/tag/v1.59.1 👇

🧠 What This Means for QA Engineers

This release looks tiny…

But if you’re on Windows, it fixes something painful.

⚠️ A previous change broke core developer workflows like codegen, --ui, and show.

This patch reverts that behavior — restoring stability where it matters most.

🔑 Key Improvement 1 — Restored Stability for Codegen & UI Tools (Windows)

What changed:
Playwright reverted hiding the console window when spawning browser processes on Windows.

Why this was needed:
The earlier behavior caused regressions:

• codegen stopped working properly
• --ui mode became unreliable
• show command broke in some cases

👉 Basically: core debugging + test creation workflows were disrupted

My expert take:
This is not a minor issue.

• codegen is widely used for test generation
• UI mode is critical for debugging flaky tests

Breaking these = slowing down entire QA teams.

How it helps QA engineers:

• Restores developer productivity
• Fixes broken local debugging workflows
• Makes test creation smooth again

🔑 Key Improvement 2 — Better OS-Specific Reliability

What changed:
Playwright now respects Windows-specific behavior instead of forcing a cross-platform assumption.

Why this was needed:
What works on macOS/Linux doesn’t always work on Windows — especially with process handling and UI rendering.

My expert take:
👉 This shows maturity.

Frameworks that ignore OS differences eventually break in enterprise setups.

How it helps QA engineers:

• More predictable behavior across environments
• Fewer “works on my machine” issues
• Better support for Windows-heavy teams

⚠️ Any Breaking Changes — What You Should Know

Good news:
👉 No breaking changes in this release.

This is a pure bug fix / regression rollback.

But here’s the nuance:

• If you relied on hidden console behavior (rare), you might notice the console window again
• Mostly, this is a fix — not a change you need to adapt to

🔄 Migration Notes (Real-World Advice)

No migration needed, but you should:

• ✅ Upgrade Playwright version
• ✅ Re-test codegen, --ui, and debugging flows
• ✅ Validate local + CI environments (especially Windows agents)

👉 Think of this as a “restore sanity” update

🧠 My Recommendation — Should You Upgrade?

✔ YES — Upgrade immediately IF:

• You’re using Windows
• Your team relies on codegen or UI mode
• You experienced recent regressions

⏳ Lower priority IF:

• You’re fully on macOS/Linux
• You didn’t hit these issues

💡 Final Thought (Use This as Your Punchline 🔥)

“This Playwright update doesn’t add features —
it brings back something more important:
a workflow that just works.”

This article is part of QA Pulse by SK — your weekly signal for QA, Test Automation and AI in Software Engineering. Subscribe free.