TestersAI.NUnit
The easiest way to AI-upgrade your existing NUnit 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.Instantiate TestersAIFixture in your test; use TestersAIAssert.Clean(r) for hard assertions.
# Download testersai-csharp-nunit-0.1.0.tar.gz from the Downloads page, then:
tar -xzf testersai-csharp-nunit-0.1.0.tar.gz
cd testersai-csharp-nunit-0.1.0
dotnet add <your.csproj> reference ./Core/TestersAI.Core.csproj
dotnet add <your.csproj> reference ./NUnit_TestersAI/
A complete, runnable C# / .NET + NUnit example.
using NUnit.Framework;
using TestersAI.NUnitSupport;
public class CheckoutTest {
TestersAIFixture _ta;
[SetUp] public void S() => _ta = new TestersAIFixture();
[Test] public async Task Checkout() {
var r = _ta.Wrap(await _ta.Client.AnalyzeScreenshotAsync(
"cart.png"));
TestersAIAssert.Clean(r);
}
}
Output goes through TestContext.WriteLine; Assert.Fail for clean-check.
If the AI call fails — rate limit, hang, firewall, no network — the SDK gives up
fast and returns a skipped result. Your NUnit test is never blocked.
Rule of thumb: wherever a human reviewer would pause to look during a manual run. These recommendations are tuned for NUnit — 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.
TestContext.WriteLine; Assert.Fail for clean-check.Or grab the monolith ZIP (all languages, all adapters).