Self-healing selectors for the test suite you already have.

What self-healing actually means

Pass a natural-language description alongside your CSS selector. When the selector misses, LumaBrowser routes the request to an LLM with a cleaned snapshot of the live DOM and asks for the matching element. The locator comes back, the test step executes, the run stays green. You learn about the rename from a log line, not a Slack alert.

Three lines you change. Nothing else.

Pick your stack. Each tab below is the entire migration: a connection URL and one capability or domain call. Your locators, your assertions, your fixtures, your CI — all unchanged.

# Same WebDriver URL as ChromeDriver. Add one capability.
from selenium import webdriver

opts = webdriver.ChromeOptions()
opts.set_capability(
    "lumabyte:llmFallback",
    {"enabled": True}
)

driver = webdriver.Remote(
    "http://127.0.0.1:9515",  # LumaBrowser's W3C WebDriver server
    options=opts
)

# Existing test code — locators, assertions, waits — unchanged.
driver.find_element(
    By.CSS_SELECTOR, ".btn-primary",
    # Optional per-call hint that survives renames.
).click()

// connectOverCDP attaches to LumaBrowser unchanged.
import { chromium } from 'playwright';

const browser = await chromium.connectOverCDP(
    'http://127.0.0.1:9222'
);
const page = await browser.contexts()[0].newPage();

// Existing locators keep working.
await page.click('.btn-primary');

// Or call the Lumabyte CDP domain for a description-first locator.
const cdp = await page.context().newCDPSession(page);
await cdp.send('Lumabyte.click', {
    selector: '.btn-primary',
    description: 'the primary submit button under the form'
});

// puppeteer.connect attaches to the running LumaBrowser instance.
import puppeteer from 'puppeteer-core';

const browser = await puppeteer.connect({
    browserURL: 'http://127.0.0.1:9222'
});
const [page] = await browser.pages();

// Existing CSS clicks work as-is.
await page.click('.btn-primary');

// Description-first via the Lumabyte CDP domain.
const cdp = await page.target().createCDPSession();
await cdp.send('Lumabyte.click', {
    selector: '.btn-primary',
    description: 'the primary submit button under the form'
});

What you don't have to change

Self-healing is one capability flag. Everything else in your test stack — the parts you spent years building — keeps working.

The free option in a paid market

Self-healing was an enterprise SKU until very recently. Most teams that wanted it had to migrate off Selenium / Playwright entirely and onto a managed test platform. LumaBrowser is the path that doesn't require either.

Pricing as listed by each vendor at time of publication; enterprise tiers on Mabl and Perfecto reach $40k+/year on annual contracts. Testim has a free Community tier with restricted runs and Healenium is fully open source — both are real options if you don't need self-healing across multiple drivers from a single tool. The LumaBrowser fallback is logged per-call so you can audit every hit and roll back to a strict CSS selector if you ever want to.

This comparison reflects publicly available pricing and feature information gathered to the best of our knowledge from each vendor's public materials. Vendors update plans frequently and we're a small team — if anything here looks wrong, please email [email protected] with the correction and a source, and we'll update the page.

Stack-specific deep dives

Each driver has a dedicated reference page with the full capability matrix, the supported subset of vendor extensions, and the migration FAQ. Open the one that matches your stack.