ui-testing
v1.1.0UI test case authoring and Playwright script generation for Acme CRM. buggy writes ADO Test Case work items in the team's house style; tester authors cases and generates runnable Playwright + TypeScript UI specs (forward and reverse).
By shironigun0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Oct 10, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install ui-testing for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install ui-testing@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/shironigun/claude-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/ui-testing/.
Plugin files
├── .claude-plugin/plugin.json├── skills/buggy/SKILL.md├── skills/tester/SKILL.md└── .mcp.json
Included Skills2
Write test cases for Acme CRM (Acme) tickets in the team's QA style and push them into Azure DevOps. Use this skill WHENEVER the user asks to write, draft, generate, or create test cases for an Acme CRM ticket, defect, bug, or user story — or mentions a work item ID and testing, a Test Plan/Suite, test steps, expected/actual results, or QA verification on the Agile Project project. Trigger it even if the user only says "write tests for
Review a user story, feature description, or acceptance criteria as a senior SQA analyst and write UI test cases in the team's QA house style — behavior-driven, click-by-click, every step with an explicit expected result — AND generate/parse runnable Playwright + TypeScript UI scripts for the Acme CRM automation framework, working BOTH ways (cases → scripts and scripts → cases), at the three UI levels: smoke, regression, and e2e. Use whenever the user pastes a story, ticket, AC block, feature spec, or flow description and asks for test cases, test coverage, QA review, UI automation/Playwright specs, or to convert between UI test cases and UI scripts — e.g. "write tests for this", "what should I test?", "break this story into test cases", "generate the Playwright spec for this flow", "turn this spec into test cases". UI sibling of the request/response `api-tester` skill; use `api-tester` for anything request/response and this one for click-by-click UI.
MCP servers1
- command
- cmd
- args
- /c npx -y @tiberriver256/[email protected]
- env.AZURE_DEVOPS_ORG_URL
- https://dev.azure.com/your-org
- env.AZURE_DEVOPS_AUTH_METHOD
- azure-identity
Plugin manifests1
{
"name": "ui-testing",
"version": "1.1.0",
"description": "UI test case authoring and Playwright script generation for Acme CRM. buggy writes ADO Test Case work items in the team's house style; tester authors cases and generates runnable Playwright + TypeScript UI specs (forward and reverse).",
"author": {
"name": "shironigun"
},
"keywords": [
"testing",
"qa",
"ui",
"playwright",
"test-cases",
"azure-devops",
"acme-crm"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[ui-testing on Agent Plugins Marketplace](https://pluginsmp.com/plugins/ui-testing)