Integrate Self-Healing Selenium Tests with Java.
Keep JUnit, TestNG and your existing Selenium structure. Add TestZombie as a healing layer and optionally keep successful fixes in Java code.
<dependency> <groupId>com.testzombie</groupId> <artifactId>testzombie-lib-java</artifactId> <version>1.0.0</version> </dependency> TestZombieDriver.setCredentials( "<key>", "<email>" );
Existing Selenium suite, four clear steps.
The guide starts from your current Java project instead of a framework migration.
Maven dependency
Add the TestZombie Java library to your existing Maven project.
Credentials
Configure workspace API key and account email for the integration.
Keep running tests
Existing Selenium flows and locators stay readable; the healing layer responds to suitable failures.
Keep the healing
Validated locator repairs can optionally flow back into the suite as a code update.
A healed test is good. A durably repaired test is better.
Code updates reduce the loop of finding a failure, rebuilding a locator manually and repeating the same repair in the next branch.
// healing validated // By.id("checkout-v1") By.cssSelector("[data-testid='checkout']")
Java setup FAQ
Do I have to change JUnit or TestNG?
No. The integration approach is designed to keep existing Java/Selenium suites.
Is self-healing just a fallback locator?
TestZombie connects runtime recovery with centralized healing history, analysis and optional durable code updates.
Where is the compact integration reference?
The /developer/selenium page contains the concise integration; this guide provides the broader developer explanation.