shesha-auto-testing
v1.7.2Automated end-to-end testing toolkit for Shesha framework applications. Provides skills for scaffolding Playwright test infrastructure, authoring test plans, running tests locally and on remote hubs, and syncing results to a central reports dashboard.
By Shesha2 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 25, 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 shesha-auto-testing for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install shesha-auto-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/Boxfusion/Boxfusion-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/shesha-auto-testing/.
Plugin files
├── .claude-plugin/plugin.json├── skills/create-test/SKILL.md└── skills/run-test-remote/SKILL.md
Included Skills2
Author a new markdown test plan at test-plans/<folder>/<name>.md AND a paired Playwright spec at test-plans/<folder>/<name>.spec.ts with real selectors recorded live via MCP browser. Trigger phrases include "create a test", "create a test plan", "new test for X", "test plan for Y", "add a test that...". The user provides only a title and a numbered list of high-level steps. The skill pulls App URL, environment, and credentials from CLAUDE.md, expands each step into full action steps per test-plans/RULES.md, matches the style of existing plans, AND walks each step against the real app via Playwright MCP to capture the resolved locator before writing the spec. Steps that can't be located after 2 retries fall back to a `// TODO[selector]:` marker for AI-repair on first run. The plan + spec are executed later by the run-test skill — this skill authors only, it does NOT run.
Dispatch a test plan to GitHub Actions instead of running it locally — the cloud-side workflow uses claude-code-action to drive the test, posts a Teams Adaptive Card on failure, and publishes an Allure report to gh-pages. Trigger phrases include "/Run-test-remote", "run test remote", "run on CI", "dispatch test on github actions", "run remote test", "trigger e2e workflow", "kick off the workflow". If `.github/workflows/e2e-test.yml` is missing the skill scaffolds it from a template and walks the user through wiring the required secrets (`ANTHROPIC_API_KEY`, a `<ROLE>_PASSWORD` per login role such as `ADMIN_PASSWORD`, optional `TEAMS_WEBHOOK_URL`) plus the non-secret repo variables (`TEST_ENV`, `<ENV>_APP_URL`, `<ROLE>_USERNAME`). If present, the skill picks plan(s) via the same disambiguation UX as `/RunTest`, dispatches each via `gh workflow run e2e-test.yml -f test_plan=<path>`, and prints the resulting run URL. Optional `--watch` flag blocks until the run completes.
Plugin manifests1
{
"name": "shesha-auto-testing",
"version": "1.7.2",
"description": "Automated end-to-end testing toolkit for Shesha framework applications. Provides skills for scaffolding Playwright test infrastructure, authoring test plans, running tests locally and on remote hubs, and syncing results to a central reports dashboard.",
"author": {
"name": "Shesha"
}
}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.
[shesha-auto-testing on Agent Plugins Marketplace](https://pluginsmp.com/plugins/shesha-auto-testing)