umbraco-unit-testing

Unit testing Umbraco backoffice extensions is done using @open-wc/testing and Web Test Runner. This Skill guides you through testing Lit elements, controllers, and observable patterns with either full context imports or isolated mocks.

Yes, you can test Lit elements and controllers in isolation using simplified mocking strategies. This approach allows you to write fast tests by avoiding full Umbraco context imports when they are unnecessary.

Component testing Umbraco extensions requires a Node.js environment with npm or yarn for dependency management. You must install @open-wc/testing and configure Web Test Runner to execute the tests.

To set up Web Test Runner for Umbraco Lit elements, you add the specified testing dependencies to your package.json and create a web-test-runner.config.mjs file in your project to configure execution.

The best way to verify a custom property editor is by writing component tests that check its rendering, state management, and interactions with Umbraco services using @open-wc/testing.

Yes, this testing approach supports both full Umbraco context integration and mock-based isolation strategies. You can choose to import the complete context or use mocks for faster, isolated tests.