umbraco-testing

For Umbraco extension testing, you should align your testing method with your specific development needs. Choose between unit testing, MSW mocking for API responses, mocked backoffice UI testing, or end-to-end testing against a live instance.

To test API error handling in an Umbraco dashboard, use MSW mocking to simulate API responses. This approach allows you to efficiently verify how your backoffice extension handles various API error scenarios without needing a live instance.

Use end-to-end testing for Umbraco backoffice extensions when you must validate behavior against a live Umbraco instance. This method ensures comprehensive quality assurance by testing the full system rather than mocked components.

Yes, you can use MSW to mock API responses in Umbraco testing. It is a supported strategy for mocking backoffice API interactions, allowing you to isolate and test how your extension handles specific API responses and errors.

Unit testing works for Umbraco backoffice UI extensions, but you can also choose a mocked backoffice UI testing approach. Selecting the correct method depends on aligning your testing strategy with the specific extension behavior you need to verify.