skills.rest
kraftvaerk
kraftvaerkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

umbraco-testing

Route Umbraco backoffice extension testing to specialized skills by testing level.

Updated Mar 6, 2026
Search Tags:#testing#e2e#unit test#msw#umbraco#backoffice
One-click install
npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-testing-kraftvaerk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: umbraco-testing
Source: https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy/tree/main/Kraftvaerk.Umbraco.Alchemy.Frontend/.agents/skills/umbraco-testing
Command: npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-testing-kraftvaerk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers select the most appropriate testing strategy for their Umbraco backoffice extensions, ensuring efficient and effective quality assurance.

Core Features & Use Cases

  • Testing Strategy Guidance: Provides a decision tree to guide users to the correct testing level (Unit, MSW, Mocked Backoffice, E2E).
  • Skill Routing: Acts as a router to invoke specialized testing skills based on the chosen strategy.
  • Use Case: A developer needs to test how their new Umbraco property editor handles API errors. This skill would guide them to use umbraco-msw-testing to mock the API responses.

Quick Start

Use the umbraco-testing skill to determine the best approach for testing Umbraco extension API error handling.

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?▼

MSW (Mock Service Worker) is ideal for testing Umbraco extension API error handling. It allows you to mock API responses effectively, ensuring your backoffice components handle errors correctly without relying on a live backend.

When should I use end-to-end testing for Umbraco frontend components?▼

Unit testing is best for isolating individual Umbraco frontend components. It ensures efficient quality assurance by verifying specific logic in your backoffice extensions without the overhead of broader integration tests.

Can I simulate the Umbraco backoffice UI for testing extensions?▼

Yes, you can simulate the full Umbraco backoffice UI. This approach allows you to test how your property editors and extensions behave within the actual interface environment, providing comprehensive validation.

Does this approach support testing API integrations in Umbraco?▼

Testing API integrations in Umbraco is fully supported. You can use MSW to mock API responses, allowing you to validate how your backoffice extensions handle various API scenarios and errors efficiently.

Related Skills

Explore More Software Engineering Skills→
kraftvaerkkraftvaerk

umbraco-add-extension-reference

Add Umbraco extension project references to .csproj and .sln files.

Official
Intermediate
albanistrefialbanistrefi
4

umbraco-testing

Route Umbraco backoffice extension testing scenarios to appropriate testing layers.

Community
Intermediate
kraftvaerkkraftvaerk

umbraco-property-action

Generate TypeScript code and manifest files for Umbraco property editor actions.

Official
Intermediate
1k-off1k-off
1

umbraco-testing

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

Community
Intermediate