maui-unit-testing

Unit test .NET MAUI ViewModels by targeting ViewModel state and commands directly rather than UI bindings. This approach ensures fast, deterministic tests by focusing on logic execution and mocked dependencies instead of fragile platform-specific UI components.

Mock MAUI services like ISecureStorage and IPreferences using Moq. Abstract platform-dependent services behind interfaces, including IConnectivity, IGeolocation, IFilePicker, and IDispatcher, to isolate ViewModel logic and ensure reliable unit tests.

Your .NET MAUI test project build fails because app projects need a conditional OutputType set to build as libraries for the test target framework. Create a class library test project targeting plain net9.0 or net10.0 to resolve this platform-specific build pitfall.

The best way to measure code coverage for .NET MAUI unit tests is using coverlet alongside xUnit. Add coverlet to your test project setup to generate coverage reports when running dotnet test workflows for your ViewModel and platform service tests.

You need an on-device test runner like xunit.runner.devices for .NET MAUI platform services when real platform APIs are required. For standard ViewModel logic, mocked MAUI services running on plain net9.0/net10.0 are sufficient without on-device execution.

Yes, you can use xUnit with Moq for .NET MAUI unit testing. Add xUnit, Microsoft.NET.Test.Sdk, and Moq to a class library test project targeting net9.0/net10.0 to effectively mock MAUI services and validate ViewModel commands and state.