umbraco-mocked-backoffice

Visual testing of Umbraco extensions without a .NET backend is achieved by running the backoffice UI with mocked APIs. This eliminates the need for a live server, enabling rapid iteration and UI verification in a simulated environment.

Mocking Umbraco backoffice APIs for Playwright testing is best achieved using either MSW Handlers for network-level mocking or a Mock Repository for application-level data simulation. Both approaches integrate with Vite for development.

Yes, Playwright is required to run mocked Umbraco backoffice tests. The Skill depends on @playwright/test for end-to-end testing and Vite for development server configuration to facilitate automated testing and rapid iteration.

Yes, mocked Umbraco extension testing can be integrated into CI/CD pipelines. By running tests in a controlled, mocked environment without backend deployments, the setup supports automated testing and continuous integration workflows.

To start testing your custom content editing component, run the command npm run test:mock-repo. This launches the Umbraco backoffice UI with mocked application-level data, ensuring your extension renders and interacts correctly before deployment.