umbraco-e2e-testing

Run Playwright end-to-end tests against a running Umbraco backoffice instance.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-e2e-testing-albanistrefi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-e2e-testing
Source: https://github.com/albanistrefi/umbraco_CLI/tree/main/skills/testing/umbraco-e2e-testing
Command: npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-e2e-testing-albanistrefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures your Umbraco backoffice extension works correctly across complete user journeys by running tests against a real, running Umbraco instance instead of relying on brittle UI assumptions or mocked behavior.

Core Features & Use Cases

  • Real E2E validation with Playwright: Runs end-to-end tests that cover authentication, navigation, and persistence.
  • Core-vs-extension testing approach: Uses @umbraco/playwright-testhelpers for core Umbraco operations (auth, navigation, core CRUD) and raw umbracoUi.page interactions for extension-specific UI elements.
  • Deterministic test data & teardown: Supports fast setup/cleanup using umbracoApi helpers and complex entity creation using @umbraco/json-models-builders.
  • Persistent data handling: Provides patterns for resetting Umbraco App_Data via globalSetup and a seed JSON file when your extension depends on stored state.

Quick Start

Run your Playwright E2E suite against a running Umbraco instance using environment variables for URL, login, and password, and ensure testhelpers are configured with data-mark selectors and STORAGE_STAGE_PATH for auth reuse.

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 e2e tests against a running Umbraco backoffice instance?

Playwright e2e testing for Umbraco runs against a real instance using environment variables for URL, login, and password, configured with @umbraco/playwright-testhelpers and data-mark selectors for UI automation.

How do I create deterministic test data for Umbraco backoffice extension workflows?

Deterministic test data for Umbraco workflows uses umbracoApi helpers for fast setup and cleanup, while @umbraco/json-models-builders generates complex entities for comprehensive end-to-end validation scenarios.

Does Umbraco e2e testing support authentication reuse across multiple test runs?

Umbraco e2e testing supports authentication reuse by configuring STORAGE_STAGE_PATH, enabling deterministic authenticated test runs that persist login state across Playwright test executions.

What's the best way to test custom sections and trees in the Umbraco backoffice?

Testing custom Umbraco backoffice sections and trees uses raw umbracoUi.page interactions for extension-specific UI elements, complementing core operations handled by @umbraco/playwright-testhelpers.

How do I reset Umbraco App_Data when extension tests depend on persistent stored state?

Resetting Umbraco App_Data for extension tests uses a globalSetup configuration alongside a seed JSON file, restoring persistent data state required for consistent end-to-end workflow validation.

Can I use Playwright testhelpers for core Umbraco document CRUD operations?

@umbraco/playwright-testhelpers supports core Umbraco operations including authentication, navigation, and document CRUD, providing a foundation for testing backoffice extension workflows end-to-end.