umbraco-e2e-testing

Run Playwright end-to-end tests for Umbraco backoffice extensions.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-e2e-testing-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-e2e-testing
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/umbraco-e2e-testing
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-e2e-testing-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Umbraco backoffice extensions are easy to break through UI changes, auth/token handling, selector differences, or API payload mismatches; this skill ensures your extension workflows are tested against a real running Umbraco instance.

Core Features & Use Cases

  • Runs real end-to-end tests with Playwright using Umbraco-specific fixtures for backoffice UI and API workflows.
  • Uses @umbraco/playwright-testhelpers for core Umbraco operations like authentication, navigation, and core entity CRUD, reducing brittleness caused by Umbraco’s selectors and auth state.
  • Uses raw Playwright only where needed (for your custom extension UI elements) while still leveraging testhelpers for stable core navigation and context.

Use cases: acceptance testing before release, validating persistence of data, and confirming authorization behavior for Umbraco backoffice extensions.

Quick Start

Run E2E tests against your running Umbraco instance by installing Playwright and the Umbraco testhelpers package, then executing your Playwright spec files after configuring the auth storage state and Umbraco URL.

Frequently Asked Questions about umbraco-e2e-testing

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

FAQPage Schema
How do I run Playwright end-to-end tests for Umbraco backoffice extensions?

You can validate Umbraco backoffice extension workflows by running Playwright end-to-end tests against a running Umbraco instance, using @umbraco/playwright-testhelpers for core operations and raw Playwright for custom UI elements.

Why do my Umbraco backoffice UI tests break after authentication or selector changes?

Umbraco backoffice UI tests break frequently due to auth token handling and selector differences, but using @umbraco/playwright-testhelpers with STORAGE_STAGE_PATH-based auth state and data-mark testIdAttribute handling reduces brittleness.

Can I use raw Playwright for custom extension elements while testing core Umbraco workflows?

Yes, you can use raw Playwright for custom extension UI elements via umbracoUi.page while still leveraging @umbraco/playwright-testhelpers for stable core navigation, authentication, and entity CRUD operations.

What is the best way to validate persistent data CRUD in an Umbraco backoffice extension?

The best way to validate persistent data CRUD is through end-to-end testing with Playwright using Umbraco-specific fixtures, ensuring your extension workflows are tested against a real running Umbraco instance.

Do I need a running Umbraco instance to execute backoffice e2e tests?

Yes, a running Umbraco instance is required because these end-to-end tests validate complete real user workflows, including authentication, navigation, and extension UI interactions against the live environment.

How does STORAGE_STAGE_PATH handle authentication state in Umbraco e2e testing?

STORAGE_STAGE_PATH manages authentication state in Umbraco e2e testing by persisting the auth storage configuration, allowing Playwright to maintain authenticated sessions across test runs without repeated logins.