Testers.AI SDKBETA powered by testers.ai
DocsIntegrationsFAQDownloads Get API key → Get the SDK →
Home/ Python/ Vibium
Python Vibium package: vibium_testersai

Vibium × Testers.AI

The easiest way to AI-upgrade your existing Vibium suite. You already have the tests — this adds AI Checks at the moments that matter, without replacing your framework, runner, or CI pipeline.

Download SDK Docs Jira / Xray / TestRail / Cypress Cloud

Add these AI testers to your existing tests

21 named specialists — pick by first name in any analyze_* call, or define your own.
See all + custom testers →
SharonSharonSecurityAIMarcusMarcusOWASPAIAlejandroAlejandroAccessibilityAIHiroshiHiroshiWCAGAIMiaMiaUsabilityAITariqTariqPerformanceAISophiaSophiaContentAIRichardRichardFormsAIFatimaFatimaError UXAIMeiMeiSearchAIZaraZaraNews / ContentAIYukiYukiLanding PagesAIHassanHassanCheckoutAIPriyaPriyaShopping CartAIMateoMateoPricing PagesAIPetePetePrivacy / PIIAIZaneleZaneleGDPRAIRajeshRajeshCookie ConsentAISundarSundarLegal PolicyAIJasonJasonAI Code ReviewAIDiegoDiegoAI ChatbotAI

Install

TestersAISession(session) wraps a Vibium session and duck-types against its current console/network API.

# Download the bundle from the Downloads page, then:
pip install vibium
pip install ./testersai-python-vibium-0.1.0.tar.gz

Example

A complete, runnable Python + Vibium example.

from vibium import Session
from vibium_testersai import TestersAISession

with Session() as s:
    ta = TestersAISession(s)
    ta.capture_console()
    ta.capture_network()

    s.goto("https://example.com")
    ta.analyze_screenshot()
    ta.analyze_console()
    ta.analyze_network()

How it flows

1
🧪
Your test runs
Vibium — unchanged.
2
📸
SDK captures
Screenshot, console, network, or page text.
3
🤖
Testers.AI analyses
Returns AI-identified issues.
4
📝
Vibium report
Findings shown where you already look.
5
🔗
Optional: auto-log
Jira · Xray · TestRail · Cypress Cloud.

Runs under any Python test framework — pytest, unittest, plain script. Default disk sink writes JSON. If the AI call fails — rate limit, hang, firewall, no network — the SDK gives up fast and returns a skipped result. Your Vibium test is never blocked.

Where & when to put checks

Rule of thumb: wherever a human reviewer would pause to look during a manual run. These recommendations are tuned for Vibium — pick the ones that fit your suite.

1

After every meaningful navigation

The page just re-rendered. Ask "does this look right?" before any interaction.

after page.goto() / driver.get()
2

After a state-changing action

Login, add-to-cart, toggle, submit. The UI just reflected a new state — where regressions hide.

after click / fill
3

Right before your main assertion

You were about to check one thing. Ask the AI about everything else for free.

before expect(...)
4

After async operations settle

API returned, spinner gone, toast shown. Catch broken empty-states and stale data.

after wait_for_selector
5

In teardown / afterEach

A single console + network check at the end of every test catches issues your assertions ignored.

afterEach / teardown
6

On responsive / theme switch

Mobile vs. desktop, light vs. dark, locale change. One call per viewport.

after setViewport
7

Pair with Vibium's CLI / MCP

You can also point the open SDK at a screenshot produced by vibium go on the command line, or by Vibium's MCP server — same analyze_* surface.

CLI + MCP friendly

Value: what you get for three extra lines

Download

⭐
testersai-python-vibium-0.1.0.tar.gz
Recommended. Core + the Vibium adapter — nothing else. Self-contained bundle.
~
↓
📦
testersai-python-0.1.0.tar.gz
Whole-language archive — All Python adapters.
40 KB
↓

Or grab the monolith ZIP (all languages, all adapters).

Other Python combinations

pytestunittestPlaywrightSeleniumRobot Framework