Selenium + Qirabot

Selenium suites accumulate XPath. Qirabot lets the new steps skip it: pass your existing driver, describe elements in plain English, and let AI vision locate them on the rendered page. Old tests keep running unchanged.

python

from selenium import webdriver
from qirabot import Qirabot

driver = webdriver.Chrome()
driver.get("https://www.wikipedia.org")
bot = Qirabot().bind(driver)   # bind once; the driver is stable for the session

summary = bot.extract("Get the first paragraph of the article")
print(summary)

bot.close()      # close the bot first (finishes recording/report), then the driver
driver.quit()

Selenium is not an extra — bring your own driver:

bash

pip install qirabot selenium

bind() is the natural fit

Unlike Playwright (where clicks can return new tabs), a Selenium driver object is stable for the whole session, so bind() removes the repeated first argument:

python

bot = Qirabot().bind(driver)
bot.click("the Accept Cookies button")
bot.type_text("the search box", "playwright vs selenium", press_enter=True)
ok = bot.verify("search results are shown")
rows = bot.extract("the first 5 result titles as a JSON array")

Works as a context manager too:

python

with Qirabot().bind(driver) as bot:
    result = bot.ai("Log in as demo@example.com / hunter2 and open Settings")
    assert result.success

Mixing with your existing code

python

# Old-style, stays as-is
driver.find_element(By.ID, "username").send_keys("test_user")

# New steps: no locator maintenance
bot.click("the Submit button")
assert bot.verify("a green success banner is visible")

go_back maps to history-back; navigate(driver, "example.com") prepends https:// when missing. Tab management (close_tab) is Playwright-only — on Selenium manage windows natively.

When Qirabot helps most in a Selenium suite

Assertions about rendered state (verify) where DOM checks lie — element present but invisible, overlapped, or off-screen.
Pages you don't own (payment iframes, SSO screens, captchas-adjacent flows) where selectors change under you.
One-off data pulls (extract) that would otherwise mean a parsing function per page.

Selenium + Qirabot ​

bind() is the natural fit ​

Mixing with your existing code ​

When Qirabot helps most in a Selenium suite ​

Selenium + Qirabot

bind() is the natural fit

Mixing with your existing code

When Qirabot helps most in a Selenium suite