Is Microsoft Playwright Testing retired?

Yes. Microsoft Learn states that Microsoft Playwright Testing will be retired on March 8, 2026. Teams that depended on the preview service need another way to run, observe, and manage Playwright tests.

Can I keep my existing Playwright tests?

Yes. Tynkr is designed for existing Playwright users. You can upload spec files or import from GitHub, then convert scenarios into editable workflows without rewriting the whole suite.

Is Tynkr a Playwright replacement?

No. Tynkr runs on top of Playwright. It adds managed workflows, observability, visual editing, API orchestration, alerts, and rollback around your Playwright automation.

When is raw Playwright on CI enough?

Raw Playwright on CI is enough if your team only needs code execution and can maintain reporting, alerts, test history, and debugging workflows internally. Tynkr is for teams that need those operational layers out of the box.

Microsoft Playwright Testing alternative

Migrating from Microsoft Playwright Testing?

Microsoft Playwright Testing retired on March 8, 2026. Move your existing Playwright specs to Tynkr without rewriting them, then add managed workflows, execution evidence, API checks, alerts, and version history with rollback.

Source: Microsoft Learn states that Microsoft Playwright Testing will be retired on March 8, 2026.

Import your Playwright tests free See how import works

Migration checklist

From retired service to managed workflows

1
Export or locate your existing specs
Keep your .spec.ts, .spec.js, or .spec.py files exactly as they are. You do not need to rewrite them into a proprietary format.
2
Upload files or connect GitHub
Tynkr detects Playwright test blocks, imports common actions and assertions, and creates editable visual workflows.
3
Run with evidence and alerts
Each run captures trace-ready evidence, logs, screenshots, network data, and alert policies so failures become actionable.
4
Publish with rollback
Every published workflow gets formal version history. If a change breaks production monitoring, roll back in one click.

What changed

The test runner did not disappear. The managed layer did.

Playwright itself is still strong. What disappeared is the Microsoft-managed preview service many teams used for remote execution, artifacts, and a central operational surface. Replacing that with raw CI means rebuilding reporting, alerting, run history, and failure triage yourself.

Need	Microsoft Playwright Testing	Tynkr	Raw Playwright on CI
Existing Playwright specs	Supported before retirement	Import as editable workflows	Run directly
Managed execution UI	Retired	Built in	Build and maintain yourself
Trace and failure evidence	Limited to service artifacts	Screenshots, logs, network, run evidence	Configure in CI
Version history rollback	No current service	Built in	Manual git revert or custom process
Failure alerts	No current service	In-app and email policies	Custom integration required
API plus browser orchestration	No current service	Built in	Separate tools required

Import existing Playwright specs

Bring in the tests your team already wrote. Tynkr turns each scenario into a managed workflow instead of forcing a rewrite.

Full execution evidence

Review screenshots, console logs, network activity, run history, and failure context without rerunning CI just to reproduce a bug.

Version history and rollback

Publish creates immutable versions. Manual checkpoints let teams mark safe states before risky edits.

Failure alerts

Configure in-app and email alerts with recipients, trigger scope, thresholds, and cooldowns without adding messaging nodes.

Browser plus API orchestration

Chain browser workflows with API collection checks, conditions, and scheduled synthetic monitoring in one product.

Governance for production targets

Protected Environments add confirmation, OTP, audit events, and blocking for risky production automations.

Migration path

A practical 30-minute migration plan

Start by importing a small smoke suite instead of moving everything at once. Prove that your most critical Playwright checks run with evidence, alerts, and rollback. Then expand coverage.

Export or locate your existing specs

Keep your .spec.ts, .spec.js, or .spec.py files exactly as they are. You do not need to rewrite them into a proprietary format.

Upload files or connect GitHub

Tynkr detects Playwright test blocks, imports common actions and assertions, and creates editable visual workflows.

Run with evidence and alerts

Each run captures trace-ready evidence, logs, screenshots, network data, and alert policies so failures become actionable.

Publish with rollback

Every published workflow gets formal version history. If a change breaks production monitoring, roll back in one click.

FAQ

Microsoft Playwright Testing migration questions

Is Microsoft Playwright Testing retired?: Yes. Microsoft Learn states that Microsoft Playwright Testing will be retired on March 8, 2026. Teams that depended on the preview service need another way to run, observe, and manage Playwright tests.
Can I keep my existing Playwright tests?: Yes. Tynkr is designed for existing Playwright users. You can upload spec files or import from GitHub, then convert scenarios into editable workflows without rewriting the whole suite.
Is Tynkr a Playwright replacement?: No. Tynkr runs on top of Playwright. It adds managed workflows, observability, visual editing, API orchestration, alerts, and rollback around your Playwright automation.
When is raw Playwright on CI enough?: Raw Playwright on CI is enough if your team only needs code execution and can maintain reporting, alerts, test history, and debugging workflows internally. Tynkr is for teams that need those operational layers out of the box.

Keep Playwright. Replace the retired managed layer.

Import your first spec, run it in managed browsers, and give your team the evidence, alerts, and rollback path Microsoft Playwright Testing no longer provides.

Import your tests free Read the migration guide