Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Blazor Testing

Checked
aaronontheweb·vlatest·testing·MIT

Helps with Playwright, testing as part of testing, debugging, and quality assurance workflows.

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 aaronontheweb/dotnet-skills --skill playwright-blazor-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

aaronontheweb

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 aaronontheweb/dotnet-skills at e426ed93a9.

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

Commit
e426ed93a9
Manifest
skills/playwright-blazor/SKILL.md
Scanned
1 file, 580 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

The Playwright Blazor Testing skill enables AI agents to automate end-to-end testing for Blazor web applications using the Playwright browser automation library. It allows agents to interact with dynamic UI elements, verify rendering states, and execute complex user workflows across different browsers.

When to use it

  • Validating that Blazor components render correctly after state changes or API calls.
  • Automating regression testing for interactive forms and navigation flows in .NET web apps.
  • Verifying cross-browser compatibility for Blazor Server, WebAssembly, and Hybrid applications.
  • Simulating real user interactions like clicking buttons, typing text, and verifying popups.

Key capabilities

  • Integration with Playwright's robust browser automation engine.
  • Support for all major browsers (Chromium, Firefox, WebKit).
  • Ability to handle asynchronous Blazor state updates.
  • Execution of end-to-end test scenarios within CI/CD pipelines.

Example prompts

  • "Create a Playwright test script to verify that the login button on my Blazor app redirects to the dashboard upon successful authentication."
  • "Automate a regression test suite for the checkout flow in this Blazor WebAssembly application, including form validation and payment processing."
  • "Write a test to ensure that dynamic data tables in my Blazor Server app update correctly when new records are added via an API."

Tips & gotchas

Ensure your Blazor project is running on a server or configured for headless execution before running automated tests. This skill requires the Playwright NuGet packages and appropriate browser binaries to be installed in your test environment.