WinUia.NUnit
0.1.0
dotnet add package WinUia.NUnit --version 0.1.0
NuGet\Install-Package WinUia.NUnit -Version 0.1.0
<PackageReference Include="WinUia.NUnit" Version="0.1.0" />
<PackageVersion Include="WinUia.NUnit" Version="0.1.0" />
<PackageReference Include="WinUia.NUnit" />
paket add WinUia.NUnit --version 0.1.0
#r "nuget: WinUia.NUnit, 0.1.0"
#:package WinUia.NUnit@0.1.0
#addin nuget:?package=WinUia.NUnit&version=0.1.0
#tool nuget:?package=WinUia.NUnit&version=0.1.0
WinUia.NUnit
NUnit integration for WinUia: [UiTest] gives each UI test the desktop to itself (also across parallel test
processes) and puts it in the UI category; Eventually(...) waits for UI state the app updates asynchronously.
The package adds using WinUia.NUnit; and using static WinUia.NUnit.UiAssertions; to your project
(turn off with <WinUiaImplicitUsings>false</WinUiaImplicitUsings>).
dotnet add package WinUia.NUnit
using NUnit.Framework;
using WinUia;
[assembly: Apartment(System.Threading.ApartmentState.MTA)] // UI Automation needs MTA threads
// MyApp: your App subclass (executable path and defaults), see the WinUia README
[UiTest]
public class MainFormTests
{
private MyApp _app = null!;
[SetUp] public void SetUp() => _app = App.Launch<MyApp>();
[TearDown] public void TearDown() => _app.Dispose();
[Test]
public void Clicking_shows_the_result()
{
_app.Find("btnClick").Click();
Eventually(() => _app.Find("lblResult").Name == "Clicked");
}
}
Run everything except UI tests with dotnet test --filter "Category!=UI".
Documentation: https://github.com/buning-software/win-uia
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0-windows7.0 is compatible. |
-
net10.0-windows7.0
- NUnit (>= 4.3.2)
- WinUia.Core (>= 0.1.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0 | 0 | 10/6/2026 |