All 7 Best Practices & Architecture questions
More in Best Practices & Architecture
What are general best practices for a maintainable MAUI app? How should you organize code in a MAUI project? How do you implement a navigation service to keep view models testable? How do you handle errors and show user-friendly messages centrally? What logging and observability practices suit a MAUI app? How do you decide between native MAUI, Blazor Hybrid, and hybrid approaches for a project?
Advertisement
Back to results for “UI Testing”
.NET MAUI › Best Practices & Architecture

How do you keep a MAUI codebase testable and loosely coupled?

Advanced

Answer

Depend on interfaces (services, navigation, dialogs, device features) injected via DI; keep view models free of platform and UI types; use the MVVM Toolkit for commands/observables; and put integration-heavy code behind seams you can fake. Aim for the bulk of behavior to be unit-testable without a device.
public OrdersViewModel(IOrderService svc,
    INavigationService nav, IDialogService dialogs) { /* all injected */ }
Real-world example Because every dependency is an injected interface, the orders view model is fully unit-tested with mocks.

Common follow-ups: What types should view models avoid? | What is a test seam?

Architecture Testing & Debugging Best Practices & Architecture
All 7 Best Practices & Architecture questions