TestersAI.Selenium
The easiest way to AI-upgrade your existing Selenium (.NET) 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 TestersAIDriver(driver, log => ...). Pulls browser logs via driver.Manage().Logs.GetLog("browser").
# Download testersai-csharp-selenium-0.1.0.tar.gz from the Downloads page, then:
tar -xzf testersai-csharp-selenium-0.1.0.tar.gz
cd testersai-csharp-selenium-0.1.0
dotnet add <your.csproj> reference ./Core/TestersAI.Core.csproj
dotnet add <your.csproj> reference ./Selenium_TestersAI/
A complete, runnable C# / .NET + Selenium (.NET) example.
using IWebDriver driver = new ChromeDriver();
driver.Navigate().GoToUrl("https://example.com");
var ta = new TestersAIDriver(driver,
r => TestContext.WriteLine($"[ta] {r.Issues.Count}"));
var shot = await ta.AnalyzeScreenshotAsync();
Assert.IsFalse(shot.Failed);
Any Action<AnalysisResult> callback you pass in.
If the AI call fails — rate limit, hang, firewall, no network — the SDK gives up
fast and returns a skipped result. Your Selenium (.NET) test is never blocked.
Rule of thumb: wherever a human reviewer would pause to look during a manual run. These recommendations are tuned for Selenium (.NET) — 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.
Action<AnalysisResult> callback you pass in.Or grab the monolith ZIP (all languages, all adapters).