Automatic Code Update
Heal at runtime. Fix it permanently in code.
TestZombie can optionally write successful healings for Selenium, Playwright and Appium directly back to test source. Healing does not only save the current run — the fix stays.
Selenium · JavaPlaywright · TypeScriptAppium · Android & iOS
// TestZombie healed 2026-09-28 // driver.findElement(By.id("checkout-v1")).click(); driver.findElement(By.cssSelector("[data-testid='checkout']")).click();
TestZombie Difference
Turn a temporary healing into a durable fix.
The original locator stays traceable, the healed locator is added, and the update can flow through your normal review and Git workflow.
1Locator breaksThe existing test can no longer find the expected element.
2TestZombie healsThe strongest candidate is found, evaluated and validated during the run.
3Fix is documentedOriginal locator, replacement and healing context remain traceable.
4Source is updatedOptionally, the successful fix is written directly back into the Selenium, Playwright or Appium test.
Cross Stack
One feature. Three stacks.
Do not repair the same locator twice.
TestZombie heals the run — and can write the successful fix directly back into your test source.