Home/ JavaScript

⚙️ JavaScript 7 adapters import: @testersai/sdk

JavaScript / TypeScript — async/await — naturally

Core returns Promises. Every adapter wraps fetch-level concerns so your test just awaits a result. Three lines of SDK code layer AI checks onto your existing JavaScript / TypeScript suite — same tests, same CI, same report; now with AI Checks at the moments you choose.

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 →

The flow in JavaScript / TypeScript

1

🧪

Your test runs

JavaScript / TypeScript — unchanged.

2

📸

SDK captures

Screenshot, console, network, or page text.

3

🤖

Testers.AI analyses

Returns AI-identified issues.

4

📝

JavaScript / TypeScript report

Findings shown where you already look.

5

🔗

Optional: auto-log

Jira · Xray · TestRail · Cypress Cloud.

Pick your framework

One self-contained page per combination. Shareable URL, everything you need to start.

⚙️ JavaScript

@playwright/test

Use TestersAIPage or the exported test fixture.

See install + example →

⚙️ JavaScript

Cypress

Register tasks in cypress.config.js, import commands in support/e2e.js.

See install + example →

⚙️ JavaScript

Puppeteer

new TestersAIPage(page) wraps the puppeteer Page and hooks console/response events.

See install + example →

⚙️ JavaScript

Jest

require('@testersai/jest') in a setup file listed under setupFilesAfterEnv. Registers the toBeTestersAIClean() matcher globally.

See install + example →

⚙️ JavaScript

Mocha

createHelper() returns a wrapper with screenshot / console / network / pageText / assertClean.

See install + example →

⚙️ JavaScript

WebdriverIO

Add the service to wdio.conf.js. Injects browser.testersai*() commands.

See install + example →

⚙️ JavaScript

Vibium

new TestersAISession(session) wraps a Vibium session and hooks console/network via its event emitter.

See install + example →

Where & when to put AI checks

Universal across JavaScript / TypeScript frameworks. Tune to your specific adapter on its own page.

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