Automatic Code Update
Heal at runtime. Fix it permanently in code.
A test continues thanks to self-healing – but the same element should not need to be rediscovered next time. TestZombie can optionally write successful locator repairs back into existing test code so the fix is retained.
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.
Without a lasting update, the test may have to rediscover the same element on a later run. A reviewed code fix can reduce repeated repair work.
1Locator breaksA test looks for the previous checkout button locator, which changed after a release.
2TestZombie healsTestZombie checks which element likely matches the original button after the change.
3Fix is documentedYou can trace which locator stopped working and which alternative was used.
4Source is updatedWhen enabled, a successful fix can be saved to your existing test code and reviewed later.
Cross Stack
One feature. Three stacks.
Do not repair the same locator twice.
Reduce repeated repairs in the same place: successful locator fixes can optionally be saved in your existing code.