Playwright · Automatic Code Update

Locator healed? Put the fix back into your Playwright test.

Runtime healing keeps the current run alive. Automatic Code Update turns a validated healing into a durable, reviewable TypeScript fix.

TypeScriptReviewable FixHealing History

checkout.spec.ts

// TestZombie healed locator
// await page.locator('#checkout-v1').click();
await page.getByTestId('checkout').click();

⚡

Save the run

When a locator breaks after a UI change, TestZombie can use a sufficiently reliable replacement.

↻

The successful locator can optionally be written back into the affected test file.

🔎

Original locator, replacement and healing context remain visible for review and later analysis.

Heal once. Keep the fix.

The code-update flow connects runtime recovery with normal engineering review instead of hiding healing in a black box.

1Playwright locator breaksThe existing locator no longer finds the expected UI element.

2Healing is validatedTestZombie evaluates candidate elements and only uses a sufficiently reliable match.

3Healing is documentedOriginal, replacement and context stay visible in the healing history.

4TypeScript code is updatedOptionally, the successful fix is written into the test file and can go through normal review.

Playwright

The complete Playwright product story for self-healing, analysis and lower maintenance.

Step-by-step from npm and imports to healing and durable fixes.

Compact integration page for existing Playwright projects.

FAQ

No. Automatic Code Update is an optional workflow; teams can combine runtime healing and durable code changes with their own review process.

The code-update approach is designed for traceability: original locator, healing context and replacement should remain reviewable.

No. The value is in preparing and documenting repetitive locator repairs while normal quality and review processes can remain in place.

Turn validated healings into durable TypeScript fixes inside the Playwright project you already use.