Umbraco Testing

This is a routing skill that helps you pick the right testing approach for Umbraco backoffice extensions. It doesn't do the testing itself. Instead, it analyzes what you're trying to test and points you to one of four specialized skills: unit testing for isolated components, MSW testing for API mocking, mocked backoffice for UI integration without a backend, or E2E for full workflows. The decision guide is solid and the tree-example reference shows all four levels working together with 32 tests total. If you're building Umbraco extensions and tired of guessing which testing tool to reach for, this gives you a clear map of when to use what.

skills.sh installs: 368
GitHub stars: 27
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Umbraco Testing - Router

Entry point for testing Umbraco backoffice extensions. Use this skill to determine which testing approach to use, then invoke the appropriate specialized skill.

Quick Reference

Level	Skill	Use When
1	`umbraco-unit-testing`	Testing contexts, elements, controllers in isolation
2	`umbraco-msw-testing`	Testing API error handling, loading states
3	`umbraco-mocked-backoffice`	Testing extension UI in full backoffice (no .NET)
4	`umbraco-e2e-testing`	Testing complete workflows against real Umbraco

Supporting Skills

Skill	Purpose
`umbraco-test-builders`	JsonModels.Builders for test data
`umbraco-playwright-testhelpers`	Full API reference for testhelpers
`umbraco-example-generator`	Generate testable example extensions