manual-testing-guide

This Skill streamlines manual testing by generating a TESTING.md file that maps code changes to testable surfaces including user interfaces, APIs, and CLI commands. It structures test cases by priority and category to ensure all critical paths and edge cases are covered before deployment.

The best way to structure user acceptance testing is by categorizing test cases by priority and testable surface area. This Skill generates a guide covering critical paths, edge cases, and error handling, while providing structured sections for QA engineers to record pass/fail status and feedback notes.

Yes, you can use this manual testing guide for validating API and CLI command changes. The Skill explicitly maps code modifications to various testable surfaces including APIs, CLI commands, and user interfaces, ensuring comprehensive validation coverage across all modified components before deployment.

A QA engineer documents test results and bugs using the structured feedback sections provided in the generated TESTING.md file. The guide supplies clear areas for testers to record pass/fail status and detailed notes, streamlining the collection of validation feedback and bug reports for the development team.

You need to generate a manual testing guide when thorough user acceptance testing is required before deployment. This Skill facilitates manual validation by mapping code changes to testable surfaces and structuring test cases by priority, ensuring critical paths, edge cases, and error handling are explicitly covered.