umbraco-testing

Testing Umbraco backoffice extensions requires choosing between unit testing, MSW testing, mocked backoffice testing, and end-to-end testing based on specific requirements like isolated contexts, API error handling, UI integration, or full workflow validation.

Choose unit testing for isolated contexts and mocked backoffice testing for UI integration. Use E2E testing when you need full workflow validation against a real Umbraco environment, while MSW testing handles specific API error handling scenarios.

You need MSW testing for an Umbraco extension when your specific testing requirements involve API error handling and simulating network responses, rather than testing full UI integration or complete end-to-end workflows.

Yes, you can generate test data and facilitate testing using test builders and test helpers, which support the various testing strategies from unit tests to full end-to-end workflows for Umbraco extensions.

Yes, Umbraco testing supports all layers of the testing pyramid for robust extension validation, providing structured guidance across unit, MSW, mocked backoffice, and end-to-end testing levels.

A testing strategy router for Umbraco extensions guides you to the most appropriate testing level for your specific scenario, preventing over-testing with E2E when isolated unit tests or mocked backoffice tests are sufficient.