manual-testing

Validates implemented features by exercising API endpoints with curl and frontend flows with agent-browser.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tsmes/conaro --skill manual-testing-tsmes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-testing
Source: https://github.com/tsmes/conaro/tree/main/.claude/skills/manual-testing
Command: npx skills add https://github.com/tsmes/conaro --skill manual-testing-tsmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a feature, you need hands-on confirmation that it actually works from a user's perspective, not just that unit tests pass. This Skill provides a structured workflow for manually verifying API endpoints and frontend behavior against the original plan, then recording results in a reproducible test report. ## Core Features & Use Cases - API Testing with curl: Exercise REST endpoints for happy paths, error cases, and side effects, capturing status codes and JSON responses. - Frontend Testing with agent-browser: Drive a real browser to fill forms, click elements via snapshot refs, take screenshots, and save/restore authenticated session state. - Structured Test Reports: Record pass/fail results, reproduction steps for failures, and screenshots in a markdown report saved next to the plan file. - Use Case: After implementing a user registration endpoint and form, run the app, POST valid and invalid payloads with curl, walk through the signup flow in a browser, and produce a test-results document confirming the feature meets its acceptance criteria. ## Quick Start Manually test the feature described in the current plan by running the app, exercising its API endpoints with curl, verifying the frontend flow with agent-browser, and writing a test report next to the plan file.

Frequently Asked Questions about manual-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually test a REST API endpoint with curl?▼

Test the happy path first with a valid request, then probe error cases like missing fields and unauthorized access. Use -s with jq for readable output and -w '\n%{http_code}\n' to capture status codes, and verify side effects with a GET after a POST.

How do I test frontend behavior with agent-browser?▼

Open the page with agent-browser open, run snapshot -i to get interactive element refs like @e5, then use fill and click against those refs. Re-snapshot after navigation since refs are invalidated, and capture screenshots as evidence.

How do I test authenticated pages without logging in every time?▼

Log in once through the browser, then run agent-browser state save auth.json to persist the session. Later runs can restore it with agent-browser state load auth.json before navigating to protected pages.

What should I do when a manual test fails?▼

Do not fix the issue immediately. Record the failure with reproduction steps, expected versus actual behavior, and a screenshot if applicable, then continue testing to get a complete picture before returning to implementation.

When is manual testing not the right approach?▼

Manual testing validates user-facing behavior, not internal implementation details, and is not a substitute for unit or integration tests. It also stops once you have confidence the feature works rather than exhaustively covering every scenario.