skills.rest
albanistrefi
albanistrefiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

umbraco-testing

Route Umbraco backoffice extension testing scenarios to appropriate testing layers.

4|Updated Mar 6, 2026
Search Tags:#unit testing#testing strategy#e2e testing#msw#umbraco#backoffice extensions#test routing
One-click install
npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-testing-albanistrefi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: umbraco-testing
Source: https://github.com/albanistrefi/umbraco_CLI/tree/main/skills/testing/umbraco-testing
Command: npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-testing-albanistrefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Choose an effective testing approach for Umbraco backoffice extensions without wasting time setting up the wrong level of testing for the problem you’re trying to solve.

Core Features & Use Cases

  • Testing pyramid routing: Guides you to the correct testing level (unit, MSW, mocked backoffice, or full E2E) based on what you need to validate.
  • Outcome-focused decision guide: Maps common scenarios (context/state logic, API error handling, UI integration, and complete workflows) to the fastest appropriate method.
  • Companion skill selection: Points to specialized skills for generating test data and test builders so your tests stay consistent and context-aware.

Quick Start

Tell the AI what you’re testing (for example: API error handling, UI integration, or a full workflow) and it will recommend the right Umbraco testing level and the next specialized skill to run.

Frequently Asked Questions about umbraco-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to test Umbraco backoffice extensions?▼

To test Umbraco backoffice extensions effectively, map your specific scenario to the correct testing layer, choosing between unit isolation, MSW API mocking, mocked backoffice UI checks, or full E2E workflows.

How do I choose between unit testing and E2E testing for Umbraco?▼

Choose between unit and E2E testing for Umbraco by routing based on your goal: use unit tests for context and state logic, MSW for API error handling, and full E2E only for complete acceptance workflows with real Umbraco.

When should I use MSW for testing Umbraco extensions?▼

You should use MSW for testing Umbraco extensions when you need to validate API error handling and mocked API behavior, allowing you to isolate network interactions without spinning up a full end-to-end environment.

Can I test Umbraco UI integration without a real backoffice environment?▼

You can test Umbraco UI integration without a real backoffice by using a mocked backoffice environment, which provides realistic UI checks for your extensions while avoiding the overhead of a full Umbraco server setup.

How do I generate test data for Umbraco extension testing workflows?▼

Generate test data for Umbraco extension testing by delegating execution to specialized companion skills after routing, ensuring your test builders and data generation remain consistent and context-aware across the testing pyramid.

Related Skills

Explore More Software Engineering Skills→
1k-off1k-off
1

umbraco-testing

Route Umbraco backoffice extension tests to unit, mocked UI, or E2E levels.

Community
Intermediate
skaile-aiskaile-ai

test-plan

Generate a per-package TEST_PLAN.md with coverage gaps and scenario seeds.

Official
Intermediate
umbracoumbraco
26

umbraco-testing

Select testing strategies for Umbraco backoffice extensions.

Official
Intermediate
albanistalbanist
4

umbraco-testing

Route Umbraco backoffice extension testing to specialized unit, MSW, mocked UI, or end-to-end skills.

Community
Intermediate