umbraco-msw-testing

Mock Umbraco backoffice API calls for testing UI error states by intercepting network requests with MSW v2 handler patterns. This enables deterministic testing of 404/500 errors, validation failures, and delayed responses without a live CMS instance.

Test Umbraco backoffice extensions without a running instance by using Mock Service Worker to intercept API calls. This enables integration-style tests with browser-focused tooling like @web/test-runner and Playwright to verify UI behavior.

Simulate loading and empty results in Umbraco UI tests by configuring MSW handlers to return delayed responses or empty data sets. This verifies loading indicators and empty state rendering without relying on actual backend data conditions.

Set up stateful mock data for Umbraco CRUD operations by driving an in-memory mock database with MSW handler overrides per test. Reset the mock database between tests to ensure deterministic integration-style testing of backoffice extensions.

MSW v2 supports intercepting Umbraco API paths for validation error testing through dedicated handler patterns and path helpers. It provides a mock worker setup lifecycle to return specific validation errors and verify backoffice UI handling.

Use @web/test-runner and Playwright for Umbraco element-level testing to execute browser-focused tests against mocked API responses. This combination verifies backoffice extension rendering across loading, success, empty, and error states without a CMS backend.