Skip to content
TrustedSkillsbeta
Back to all skills

Umbraco Testing

Checked
umbraco·vlatest·testing

Automates Umbraco website content and functionality tests, ensuring quality and reducing manual regression efforts.

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-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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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-testing/SKILL.md
Scanned
1 file, 154 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, umbraco-testing, acts as a central entry point for testing Umbraco backoffice extensions. It doesn't perform tests directly but guides you to select the appropriate specialized testing skill based on your needs. The available options include unit testing, Mock Service Worker (MSW) API testing, mocked backoffice UI testing, and end-to-end (E2E) testing.

When to use it

Here are some scenarios where this skill would be helpful:

  • You need to test the logic within a Umbraco extension in isolation without needing a full backend setup.
  • You want to verify API error handling and loading states without interacting with a live server.
  • You're developing an extension and need to ensure its UI elements appear correctly within the Umbraco backoffice environment.
  • You require comprehensive testing of complete user workflows against a real Umbraco installation.

Key capabilities

  • Test Selection Guidance: Provides a decision guide to help users choose between umbraco-unit-testing, umbraco-msw-testing, umbraco-mocked-backoffice, and umbraco-e2e-testing.
  • Skill Routing: Directs the agent to the appropriate specialized testing skill based on the chosen approach.
  • Supports Related Skills: Integrates with supporting skills like umbraco-test-builders (for test data), umbraco-playwright-testhelpers, and umbraco-example-generator.

Example prompts

Here are some example prompts you could give an AI agent equipped with this skill:

  • "I need to test the logic of a controller in my Umbraco extension."
  • "How can I test API error handling for my Umbraco backoffice extension?"
  • "What's the best way to ensure my new UI element appears correctly in the Umbraco backoffice?"

Tips & gotchas

  • This skill is a router, not a tester itself. You will need to select and use one of the linked specialized testing skills.
  • The choice of testing approach depends on what you're trying to test; consider the speed and backend requirements outlined in the decision guide.
  • Familiarity with Playwright and potentially MSW (for API testing) may be helpful depending on your chosen testing method.