Developer Hub

Developer Hub for resilient test automation

Everything you need to integrate TestZombie.AI into Selenium, Playwright and Appium projects.

Built for automation developers. Designed for enterprise teams.

Quick start

Get started in under 5 minutes

1. Add library

Add the TestZombie library that matches your test framework.

2. Set credentials

Set your API key and user email directly on TestZombieDriver.

3. Run your first test

Keep running Selenium, Playwright or Appium on your own infrastructure.

4. Keep your tests alive

Use healing, analysis and recommendations when TestZombie services are needed.

Quick Start

Start with Selenium, Playwright or Appium

Keep your existing automated tests and add TestZombie as the intelligence layer for healing, analysis and fix recommendations.

📦

Maven

Add TestZombie to your pom.xml and keep your setup reproducible.

View snippet

☕

Libraries & Examples

Libraries, integrations and example projects for Selenium, Playwright and Appium.

Open GitHub

📚

Documentation

Installation, configuration, healing and billing guides.

Browse docs

Code snippets

Copy & paste integration snippets

Use these examples as a starting point. Selenium uses the Java library; Playwright is integrated through the npm package.

pom.xml

<dependencies>
    <dependency>
        <groupId>com.testzombie</groupId>
        <artifactId>testzombie-lib-java</artifactId>
        <version>1.0.0</version>
    </dependency>
</dependencies>

Driver initialization

TestZombieDriver.setCredentials("<key>","<email>");
WebDriver driver=TestZombieDriver.createChrome();

Playwright npm

npm install @testzombie/playwright

Playwright Integration

Selenium Web

Web tests with Selenium and TestZombie healing.

Java · Selenium · Chrome

Selenium Example

Playwright Web

Modern web tests with Playwright and TestZombie healing.

TypeScript · Playwright · Chromium / Firefox / WebKit

Playwright Integration

Appium Android

Android tests with Appium and mobile healing.

Java · Appium · Android

Android Example

iOS

Appium iOS

iOS tests with Appium and platform-specific healing.

Java · Appium · iOS

iOS Example

Documentation

Developer documentation

The core topics for Selenium, Playwright and Appium teams — from setup to troubleshooting.

Getting Started

Quickstart

Add the matching library, set credentials and keep using your existing test framework.

Dependency

Add selenium-java to your existing Maven project.

Credentials

Set API key and account email once before creating the driver.

Run

Use the TestZombie integration and keep your existing test flows.

Driver initialization

TestZombieDriver.setCredentials("<key>","<email>");
WebDriver driver=TestZombieDriver.createChrome();

Selenium

Selenium integration

TestZombie is designed as an intelligence layer around existing Selenium tests. Your By locators and test flow stay readable and familiar.

Good to knowIf TestZombie cannot heal an element, normal Selenium behavior remains the fallback.

First healing-ready test

@Test
void loginShouldWork() {
    driver.get("https://example.test/login");
    driver.findElement(By.id("email")).sendKeys("qa@example.com");
    driver.findElement(By.id("password")).sendKeys("secret");
    driver.findElement(By.cssSelector("button[type='submit']")).click();
}

Playwright

Playwright integration

Set up the TestZombie Playwright integration in three steps: install the npm package, replace the Playwright import, and set your API key and email in the Playwright configuration.

1. Install the package

npm install @testzombie/playwright

2. Replace the import

Replace the existing import from @playwright/test with @testzombie/playwright.

import { test, expect } from '@playwright/test';

import { test, expect } from '@testzombie/playwright';

3. Set API key & email

Set the API key and email in your Playwright configuration.

process.env.TESTZOMBIE_API_KEY = '';
process.env.TESTZOMBIE_EMAIL = '';

Chromium

Cross-browser healing support.

Firefox

Cross-browser healing support.

WebKit

Cross-browser healing support.

Learn more about Playwright support →

Mobile

Appium: Android & iOS

Mobile tests use platform-specific element information and matching strategies while following the same TestZombie workflow.

Android

Uses resource-id, accessibility information, text and structural signals for matching.

iOS

Uses name, label, value and iOS-specific structural signals for matching.

Recommendation: prefer stable accessibility identifiers whenever your application provides them.

Configuration

Configuration without magic

Credentials identify the workspace and user. Project, environment and runtime options can then be managed centrally in TestZombie.

API keyAuthenticates calls against your TestZombie workspace.

User emailAssociates test activity with the executing account.

ProjectKeeps runs, elements and healing data separated by application.

EnvironmentDistinguishes environments such as test, staging or production-like systems.

Healing Guide

What happens during healing?

When the original locator no longer resolves the expected element, TestZombie evaluates stored element information and current candidates to find the best replacement.

1Original locator fails

2Candidates are collected and scored

3Best match is selected according to confidence

4Result and recommendation become visible in the dashboard

Rule-based firstDeterministic matching can resolve many changes without an AI call. AI can be used as an additional semantic signal when configured.

Billing & Credits

Credit usage at a glance

Credits are charged for TestZombie services, not for the execution time of your Selenium, Playwright or Appium infrastructure.

Test Run Init10

Element Update1

Element Scan2

Healing Attempt5

AI Call*5

* AI Call: 5 TestZombie Credits plus the costs of the selected AI provider.

Integrations

Connect TestZombie to your workflow

Use notifications and webhooks for operational workflows. Enterprise customers can additionally connect their own AI provider through BYOKI.

NotificationsSend relevant healing and automation events to your team.

WebhooksForward events into your own systems and automation pipelines.

BYOKIBring Your Own AI: connect OpenAI, Gemini, Mistral or a compatible endpoint and assign it to projects.

GitHubUse libraries and example projects as a practical starting point.

Troubleshooting

Common checks before debugging deeper

No connection to TestZombie?

Check API key, user email and network access to the TestZombie API.

Element is not healed?

Check whether enough element information was collected and review the healing result in the dashboard.

Mobile matching behaves differently?

Android and iOS expose different attributes. Prefer stable accessibility identifiers and inspect the stored mobile element data.

Need an example project?

The latest libraries and examples are available on GitHub. Open GitHub

Best practices

automation best practices for resilient tests

Practical guidance for stable locators, maintainable page objects and fewer flaky failures.

Stable locators

Use attributes that describe intent, not layout.

Explicit waits

Wait for user-visible state instead of fixed timeouts.

Page objects

Keep selectors centralized, readable and easier to maintain.

Reduce flaky tests

Separate timing issues from real product defects.

FAQ

Developer FAQ

How do I integrate TestZombie?

Add the Maven dependency, set API key and email via TestZombieDriver.setCredentials(...), and start the driver with TestZombieDriver.createChrome().

What consumes Credits?

Credits are consumed when TestZombie performs intelligent services such as initialization, healing and analysis.

Rule-based vs AI Healing?

Rule-based healing uses deterministic platform logic. AI Healing adds model-assisted semantic recovery.

Do I need to rewrite my tests?

No. TestZombie is designed for existing Selenium, Playwright and Appium projects with minimal setup.

Keep your tests alive.

Start your free workspace and connect TestZombie to your automation project.

Start for free Pricing