frontend-testing

You can test Blazor components without a browser by using bUnit for component-level validation. This approach verifies component behavior and Presenters directly within your .NET testing stack, eliminating the need for a full browser environment during unit tests.

The best way to automate end-to-end testing for Blazor and MAUI apps is using Playwright combined with an AppFixture. This setup runs real backend and frontend environments to validate golden-path user journeys and reproduce UI bugs against your actual running stack.

For frontend testing, you should use stubs instead of mocks. This Skill enforces a consistent testing approach using xUnit and FluentAssertions, relying on stubs to validate UI interactions reliably without the fragility of mock objects.

To ensure stable UI selectors during Playwright E2E tests, you should enforce data-testid selectors. This practice provides reliable UI interactions by targeting dedicated test attributes rather than fragile CSS classes or dynamic DOM structures.

Yes, Playwright works with a real backend for MAUI frontend testing by using an AppFixture. This fixture spins up the actual backend and frontend environments during your test runs, ensuring realistic integration validation across your stack.

Use bUnit for unit-level component tests and Presenter validation without a browser, and use Playwright for end-to-end tests covering golden-path user journeys and UI bug reproductions. Both tools integrate within your .NET testing stack using xUnit and FluentAssertions.