umbraco-testing

Choosing the right testing strategy requires mapping your verification target to the testing pyramid, routing Umbraco extension tests to unit logic validation, MSW-mocked APIs, mocked backoffice UI, or full end-to-end workflows based on required dependencies.

Use MSW for mocked API error and loading state behavior, and use Playwright for full end-to-end workflows with real Umbraco. Select MSW to isolate controller logic and Playwright to validate complete UI integration workflows.

The best way to test API error handling is applying an MSW-mocked testing approach to intercept network requests and validate loading states and error behaviors without requiring a full Umbraco environment.

Unit testing does not cover UI integration workflows. For Umbraco backoffice extensions, route rendering and UI integration tests to mocked backoffice UI testing or full end-to-end Playwright workflows instead of isolated unit logic validation.

Build a complete testing pyramid by pairing the correct testing level with specialized skills and supporting builders, mapping scenarios from unit logic and MSW-mocked APIs up to full end-to-end workflows for repeatable test data and UI interactions.