Skip to content
TrustedSkillsbeta
Back to all skills

Umbraco Msw Testing

Listed
umbraco·vlatest·testing

Automates Umbraco website testing using Microsoft Playwright, ensuring content and functionality meet quality standards.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-msw-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

umbraco

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 5 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: feross.org, opencollective.com, paulmillr.com, paypal.me, www.patreon.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    github.comsource hostwww.patreon.comundeclaredfeross.orgundeclaredpaulmillr.comundeclaredopencollective.comundeclaredpaypal.meundeclared

    What it found (3 of 18)

    • plugins/umbraco-testing-skills/skills/umbraco-msw-testing/examples/api-mocking/package-lock.json:2136contacts www.patreon.com
      "url": "https://www.patreon.com/feross"
    • plugins/umbraco-testing-skills/skills/umbraco-msw-testing/examples/api-mocking/package-lock.json:2180contacts www.patreon.com
      "url": "https://www.patreon.com/feross"
    • plugins/umbraco-testing-skills/skills/umbraco-msw-testing/examples/api-mocking/package-lock.json:3503contacts www.patreon.com
      "url": "https://www.patreon.com/feross"

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned umbraco/umbraco-cms-backoffice-skills at 78b551bf9c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
78b551bf9c
Manifest
plugins/umbraco-testing-skills/skills/umbraco-msw-testing/SKILL.md
Scanned
12 files, 7,534 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform isolated unit and integration testing for Umbraco backoffice applications using Mock Service Worker (MSW). It allows developers to intercept and mock HTTP requests, ensuring tests run without relying on external network dependencies or a running backend.

When to use it

  • Isolate Logic: Verify specific components in the Umbraco backoffice by mocking API responses to prevent flaky tests caused by network latency.
  • Offline Development: Run comprehensive test suites locally without needing to spin up a full Umbraco instance or database connection.
  • Simulate Edge Cases: Artificially trigger error states (e.g., 500 errors, timeouts) to ensure the UI handles failures gracefully.
  • Speed Up CI/CD: Reduce build times by replacing slow live server calls with instant mock data in automated pipelines.

Key capabilities

  • Intercepts outgoing HTTP requests within the Umbraco backoffice environment.
  • Allows configuration of custom mock responses for specific endpoints.
  • Facilitates deterministic testing outcomes independent of external services.
  • Integrates directly with standard JavaScript testing frameworks.

Example prompts

  • "Set up a test suite that mocks the /api/media endpoint to return a specific image list when running Umbraco backoffice unit tests."
  • "Configure MSW to simulate a 401 Unauthorized response for the login API to verify the error handling UI in my Umbraco component."
  • "Write an integration test where I mock the CMS content delivery to ensure the dashboard renders correctly without hitting the live database."

Tips & gotchas

Ensure your test environment has MSW properly installed and configured before attempting to run tests, as the skill relies on this library for request interception. Be mindful that mocking only covers client-side logic; server-side validation or database constraints will still require a real backend or additional mock strategies.