How do I generate test data for my Umbraco tests?

The router points you toward the umbraco-test-builders skill, which provides JsonModels and Builders specifically designed for generating Umbraco test data.

Does this skill support Playwright?

Yes, it provides access to the umbraco-playwright-testhelpers skill, which contains a full API reference for testing Umbraco components with Playwright.

Can I test Umbraco extensions without a running .NET backend?

Yes, by using the 'Mocked Backoffice' or 'MSW Testing' levels, you can test extension UI and API interactions using Mock Service Worker without a live Umbraco server.

What is the Umbraco Backoffice Testing Router?

It is a specialized Claude Code skill that serves as an entry point for developers to identify and implement the correct testing strategy for Umbraco backoffice extensions.

When should I choose Unit Testing over E2E testing?

Choose Unit Testing for fast, isolated verification of logic, Lit element rendering, and state management. Choose E2E testing for full acceptance tests that require a real Umbraco backend and complete user workflows.

Umbraco Backoffice Testing Router

Name: Umbraco Backoffice Testing Router
Author: umbraco

byumbraco

•

보안 및 테스팅

Guides developers in selecting and implementing the optimal testing strategy for Umbraco CMS backoffice extensions.

소개

The Umbraco Backoffice Testing Router is a specialized architectural skill designed to streamline the quality assurance process for Umbraco developers. It provides a structured decision-making framework to help you choose between four distinct testing levels: isolated Unit Testing for logic and Lit elements, MSW Testing for API behavior, Mocked Backoffice testing for UI integration without .NET, and full E2E Testing for complete workflows. By acting as a central hub, it directs users toward the correct patterns and specialized skills required to build a robust testing pyramid for custom dashboards, property editors, and workspace actions.

주요 기능

Guidance on mocking API responses and error handling using Mock Service Worker (MSW)
1 GitHub stars
Infrastructure patterns for testing UI extensions without requiring a running .NET backend
Comprehensive decision guide for selecting Unit, MSW, Mocked, or E2E testing levels
Integration with Umbraco-specific test builders and Playwright helper libraries
Specialized routing to domain-specific skills for Lit elements and shadow DOM testing

사용 사례

Determining the most efficient testing level for a new Umbraco backoffice extension project
Simulating complex API edge cases like network timeouts or 500 errors within the CMS UI
Establishing a full testing pyramid for complex tree-based extensions using proven architectural patterns

소개

주요 기능

Guidance on mocking API responses and error handling using Mock Service Worker (MSW)
1 GitHub stars
Infrastructure patterns for testing UI extensions without requiring a running .NET backend
Comprehensive decision guide for selecting Unit, MSW, Mocked, or E2E testing levels
Integration with Umbraco-specific test builders and Playwright helper libraries
Specialized routing to domain-specific skills for Lit elements and shadow DOM testing

사용 사례

Determining the most efficient testing level for a new Umbraco backoffice extension project
Simulating complex API edge cases like network timeouts or 500 errors within the CMS UI
Establishing a full testing pyramid for complex tree-based extensions using proven architectural patterns