TestersAI.MSTest
The easiest way to AI-upgrade your existing MSTest 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.Take TestContext into the constructor; hand it to TestersAIFixture.
# Download testersai-csharp-mstest-0.1.0.tar.gz from the Downloads page, then:
tar -xzf testersai-csharp-mstest-0.1.0.tar.gz
cd testersai-csharp-mstest-0.1.0
dotnet add <your.csproj> reference ./Core/TestersAI.Core.csproj
dotnet add <your.csproj> reference ./MSTest_TestersAI/
A complete, runnable C# / .NET + MSTest example.
using Microsoft.VisualStudio.TestTools.UnitTesting;
using TestersAI.MSTestSupport;
[TestClass]
public class CheckoutTest {
public TestContext TestContext { get; set; }
TestersAIFixture _ta;
[TestInitialize] public void Init() => _ta = new(TestContext);
[TestMethod] public async Task Checkout() {
var r = _ta.Wrap(await _ta.Client.AnalyzeScreenshotAsync("cart.png"));
_ta.AssertClean(r);
}
}
TestContext.WriteLine — visible in dotnet / VS Test Explorer.
If the AI call fails — rate limit, hang, firewall, no network — the SDK gives up
fast and returns a skipped result. Your MSTest test is never blocked.
Rule of thumb: wherever a human reviewer would pause to look during a manual run. These recommendations are tuned for MSTest — 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 — visible in dotnet / VS Test Explorer.Or grab the monolith ZIP (all languages, all adapters).