Verisoft.TestInfrastructure 1.9.0-preview.1

Verisoft.TestInfrastructure

Verisoft's C# (net8.0) test-automation infrastructure for NUnit 4 + Selenium / Appium, shipped as a NuGet package.

• Driver injection: [AutofacTest] creates a fresh VerisoftDriver / VerisoftMobileDriver / VerisoftWincoreDriver per test from a capabilities factory, and quits it afterwards.
• Lifecycle extensions: [UseExtension(typeof(X))] on a fixture attaches Allure, ReportPortal, screenshot / page-source on failure, Xray JSON, an Appium server per test, property loading.
• Report bus: Report.Info(...) fans out to console, NLog, Allure and ReportPortal observers; pass a Screenshot to attach an image.
• Toolkit: Asserts / SoftAsserts, Retry, Waits, ExpectedConditions, Property / FrameworkConfig, thread-local and global Store.
• Reqnroll (Cucumber) mode: the same infra driven from hooks instead of attributes.

Install

dotnet add package Verisoft.TestInfrastructure
dotnet add package Microsoft.NET.Test.Sdk
dotnet add package NUnit3TestAdapter --version 5.2.0   # keep on 5.x, see Pitfalls

The package brings NUnit 4.6, Allure.NUnit 2.15, ReportPortal.NUnit 4.9 (including its build targets, so ReportPortal.addins is generated in your output), Appium.WebDriver 8.3, Selenium.Support 4.45, Autofac, NLog, WebDriverManager and ChromeDriver. It does not bring Microsoft.NET.Test.Sdk, NUnit3TestAdapter or Moq.

Claude Code plugin

Consumers using Claude Code can install the plugin that ships in this repository. It knows the whole API, its rules and its footguns, and can bootstrap a project (/verisoft-setup) or review tests (verisoft-test-reviewer agent):

/plugin marketplace add https://bitbucket.org/verisoft-ai/verisharp-infra.git
/plugin install verisoft-testinfra@verisharp-infra

Details: plugins/verisoft-testinfra/README.md.

Minimal project

MyTests.csproj (full version with every config file: plugin template):

<ItemGroup>
  <PackageReference Include="Verisoft.TestInfrastructure" Version="1.9.0" />
  <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.7.0" />
  <PackageReference Include="NUnit3TestAdapter" Version="5.2.0" />
  <Using Include="NUnit.Framework" />
</ItemGroup>
<ItemGroup>
  <Content Include="ReportPortal.config.json" CopyToOutputDirectory="PreserveNewest" />
  <Content Include="allureConfig.json" CopyToOutputDirectory="PreserveNewest" />
  <Content Include="NLog.config" CopyToOutputDirectory="PreserveNewest" />
  <Content Include="src\test\resources\root.config.properties" Link="root.config.properties" CopyToOutputDirectory="PreserveNewest" />
</ItemGroup>

TestAssemblySetup.cs — mandatory. The library's own [SetUpFixture] lives in a referenced DLL and NUnit never runs it in your assembly:

using NUnit.Framework;
using Verisoft.TestInfrastructure.Extensions;
using Verisoft.TestInfrastructure.Reporting;

[SetUpFixture]                       // no namespace → applies to the whole assembly
public class TestAssemblySetup
{
    [OneTimeSetUp]    public void Up()   => new PropertyLoaderExtension().BeforeSuite();   // *.properties → env vars
    [OneTimeTearDown] public void Down() => BaseObserver.DisposeObservers();
}

BrowserFactories.cs — a public static parameterless method per browser configuration:

using OpenQA.Selenium.Chrome;

public static class BrowserFactories
{
    public static ChromeOptions Chrome_Local_Headless()
    {
        var o = new ChromeOptions();
        o.AddArgument("--headless=new");
        return o;
    }
}

HomePageTests.cs:

using OpenQA.Selenium;
using Verisoft.TestInfrastructure.DriverInjection;   // the only namespace for driver attributes
using Verisoft.TestInfrastructure.Drivers;
using Verisoft.TestInfrastructure.Extensions;
using Verisoft.TestInfrastructure.Lifecycle;
using Verisoft.TestInfrastructure.Reporting;
using Verisoft.TestInfrastructure.Utils;

[TestFixture]
[Category("Browser")]
[UseExtension(typeof(LogExtension))]          // registers console + NLog observers for Report.*
[UseExtension(typeof(ScreenshotExtension))]   // PNG of every driver on failure
public class HomePageTests
{
    [AutofacTest]                              // replaces [Test]; injects and quits the driver
    [DriverCapabilities(typeof(BrowserFactories), nameof(BrowserFactories.Chrome_Local_Headless))]
    public void Title_IsNotEmpty(VerisoftDriver driver)     // void, never async Task
    {
        driver.Navigate().GoToUrl("https://example.test");
        Waits.PageToFullyLoad(driver, 10);
        Report.Info("Title: " + driver.Title);
        Assert.That(driver.Title, Is.Not.Empty);
    }
}

Run:

dotnet test --filter "TestCategory=Browser"

Feature map

Detailed, source-cited documentation for each area: plugins/verisoft-testinfra/skills/verisoft-testinfra/references/. Architecture: docs/ARCHITECTURE.md. Step by step: docs/GETTING_STARTED.md.

Pitfalls (top 10)

1. No VerisoftBaseTest. It was removed long ago; use [AutofacTest] + [UseExtension].
2. Add your own [SetUpFixture] (above). Without it properties are never loaded and observers never disposed.
3. Keep NUnit3TestAdapter on 5.x. 6.x loads tests in an isolated AssemblyLoadContext and the ReportPortal engine extension silently never runs.
4. Only Verisoft.TestInfrastructure.DriverInjection attributes work. The Drivers.Attributes / Drivers.Factory copies are [Obsolete].
5. [AutofacTest] tests must be void. An async Task is not awaited and passes instantly.
6. Missing browser or unreachable grid → test Ignored, not failed. Assert on the pass count in CI.
7. Data-driven only via [TestCase] / [TestCaseSource] (driver as null placeholder or optional last parameter). [Values] / [Range] / [Random] are rejected.
8. Everything driver-related is keyed by thread id. After an await or in Reqnroll steps call driver.EnsureRegistered().
9. SoftAsserts needs AssertAll(), otherwise failures are dropped; it throws SoftAssertionError (NUnit Error, not Failure).
10. Config files are not in the package. ReportPortal.config.json, allureConfig.json, NLog.config, capabilities.json, *.properties must be copied to the output directory; the ReportPortal API key goes in the ReportPortal_Server_ApiKey environment variable.

Full list with evidence: gotchas.md.

Repository layout

dotnet build Verisoft.TestInfrastructure.sln -c Release
dotnet test  Verisoft.TestInfrastructure.sln -c Release --filter "TestCategory=Unit" --settings ci/sequential.runsettings
dotnet test  Verisoft.TestInfrastructure.Sample/Verisoft.TestInfrastructure.Sample.csproj -c Release --filter "TestCategory=Browser" --settings ci/parallel.runsettings

License

MIT — see LICENSE.