manual-testing
SkillWeb & browsingBrowser-based manual testing of the Donut web app. Use ONLY when the developer explicitly asks to test manually or when a slice includes manual testing. Do NOT use proactively.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the manual-testing skill
What this skill tells your AI
The instructions your AI receives, as published by nerds-odd-e/doughnut in .agents/skills/manual-testing/SKILL.md and read by ahel’s review.
Purpose: Human-directed or plan-mandated exploratory testing — not a default agent workflow.
Output: Verified behavior report + summary ending with
## MANUAL TEST COMPLETE.
Prerequisites: Assume pnpm sut is already running (backend, frontend,
Mountebank — all auto-reload on code changes). If not running, suggest the user
start it in a separate terminal. To use AI services, set OPENAI_API_TOKEN
before pnpm sut.
Access points:
- Frontend: http://localhost:5173/
- Backend API: http://localhost:9081
Test accounts:
old_learner/passwordanother_old_learner/passwordadmin/password
Linting: The frontend dev server runs linting in the background. Errors appear in terminal output (overlays disabled). Check terminal and fix errors before committing.
<success_criteria>
pnpm sutrunning (or user notified to start it)- Target flows exercised via browser MCP tools
- Results verified with snapshots (and console/network if issues)
- Final output includes
## MANUAL TEST COMPLETE</success_criteria>
## MANUAL TEST COMPLETE
<out_of_scope>
- Do not run proactively without explicit developer or plan request.
- Do not substitute manual testing for automated E2E when the plan calls for Cypress. </out_of_scope>
Signals
- GitHub stars
- 49
- Forks
- 72
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
manual-testing-nerds-odd-e- Source
- github.com/nerds-odd-e/doughnut