Home/ C#

🟦 C# 5 adapters import: TestersAI.Core

C# / .NET — NUnit / xUnit / MSTest native

Uses each framework's own TestContext / ITestOutputHelper so findings show up in VS Test Explorer and dotnet test output. Three lines of SDK code layer AI checks onto your existing C# / .NET 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 C# / .NET

1

🧪

Your test runs

C# / .NET — unchanged.

2

📸

SDK captures

Screenshot, console, network, or page text.

3

🤖

Testers.AI analyses

Returns AI-identified issues.

4

📝

C# / .NET 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.

NUnit

Instantiate TestersAIFixture in your test; use TestersAIAssert.Clean(r) for hard assertions.

See install + example →

xUnit

Instantiate TestersAIFixture(outputHelper) in the constructor — findings go to xUnit's test output.

See install + example →

MSTest

Take TestContext into the constructor; hand it to TestersAIFixture.

See install + example →

Playwright (.NET)

new TestersAIPage(page). Hooks Console, PageError, and Response events.

See install + example →

Selenium (.NET)

new TestersAIDriver(driver, log => ...). Pulls browser logs via driver.Manage().Logs.GetLog("browser").

See install + example →

Where & when to put AI checks

Universal across C# / .NET 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