@testersai/vibium
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.
analyze_* call, or define your own.new TestersAISession(session) wraps a Vibium session and hooks console/network via its event emitter.
# Download testersai-javascript-vibium-0.1.0.tar.gz from the Downloads page, then:
tar -xzf testersai-javascript-vibium-0.1.0.tar.gz
cd testersai-javascript-vibium-0.1.0
npm install vibium ./testersai-sdk-0.1.0.tgz ./testersai-vibium-0.1.0.tgz
A complete, runnable JavaScript / TypeScript + Vibium example.
const { Session } = require('vibium');
const { TestersAISession } = require('@testersai/vibium');
(async () => {
const s = await Session.launch();
const ta = new TestersAISession(s);
await s.goto('https://example.com');
await ta.analyzeScreenshot();
await ta.analyzeConsole();
await s.close();
})();
Any JS test runner. Default disk sink writes JSON to ./testersai-results.
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.
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.
The page just re-rendered. Ask "does this look right?" before any interaction.
Login, add-to-cart, toggle, submit. The UI just reflected a new state — where regressions hide.
You were about to check one thing. Ask the AI about everything else for free.
API returned, spinner gone, toast shown. Catch broken empty-states and stale data.
A single console + network check at the end of every test catches issues your assertions ignored.
Mobile vs. desktop, light vs. dark, locale change. One call per viewport.
./testersai-results.Or grab the monolith ZIP (all languages, all adapters).