skills.rest
jstoup111
jstoup111COMMUNITY
Explore all skills by this author →
GitHub

manual-test

Validate implemented stories through manual curl or browser testing.

5|1|Updated Mar 30, 2026
Search Tags:#manual testing#end-to-end testing#bug reporting#story validation#TDD integration
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill manual-test-jstoup111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-test
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/manual-test
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill manual-test-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill validates the actual working of implemented stories through manual testing, ensuring the system functions end-to-end as a user would experience it.

Core Features & Use Cases

  • End-to-End Validation: Executes acceptance criteria manually to verify system functionality.
  • Correctness Enforcement: Confirms that a story passes only if its result is observed and not inferred.
  • Bug Reporting Loop: Any fail results in a bug that loops back to TDD for resolution.
  • Use Case: After a development phase, use this Skill to validate all stories using curl (API) or browser (full-stack) methods.

Quick Start

Manually test the feature 'Create a new user' by executing the curl command 'curl -s -X POST http://localhost:3000/users -H "Content-Type: application/json" -d "{"user": {"name": "John", "email": "john@example.com"}}"'

Frequently Asked Questions about manual-test

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

FAQPage Schema
How do I validate end-to-end functionality after development?▼

End-to-end functionality is validated by executing acceptance criteria manually using curl or browser testing to verify system functionality as experienced by a user.

What is manual testing for story validation?▼

Manual testing for story validation confirms implemented stories by observing actual results rather than inferring them, ensuring the system passes only when functionality is explicitly verified.

How do I handle bug reporting when manual testing fails?▼

Bug reporting during manual testing loops failed stories back to TDD for resolution, ensuring defects are addressed within the test-driven development cycle before functionality is approved.

Can I use curl for API testing or do I need a browser?▼

You can use curl for API testing or a browser for full-stack testing, depending on the project context and predefined testing protocols required to validate the stories.

When do I need manual testing in the development workflow?▼

Manual testing is needed post development to validate all stories, ensuring the system functions end-to-end and confirming that implemented features work correctly before release.

Why does a story pass only if the result is observed?▼

A story passes only if observed because correctness enforcement requires actual verification of results, preventing inferred successes from masking underlying functional defects.

Related Skills

Explore More Software Engineering Skills→
ssv445ssv445
1

test-stories

Convert Markdown user stories into automated browser acceptance tests.

Community
Advanced
picmakpropicmakpro
9

debugger

Diagnose root causes of bugs and document verified fixes.

Community
Advanced
nikblanchetnikblanchet

exhaustive-testing

Plan and implement unit, integration, regression, end-to-end, and manual test coverage.

Community
Basic
kollaboraikollaborai
1

webapp-testing

Automate local web app testing with Playwright and Python scripts.

Community
Intermediate