ln-522-manual-tester

Name: ln-522-manual-tester
Availability: InStock
Author: cbbkrd-tech

Execute bash scripts to validate Story Acceptance Criteria via API and UI tests.

Updated Mar 9, 2026

Search Tags:#test automation #acceptance criteria #manual testing #ui testing #api testing #bash scripts

Ready to run

npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-522-manual-tester-cbbkrd-tech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-522-manual-tester
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-522-manual-tester
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-522-manual-tester-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of manually verifying Acceptance Criteria (AC) for user stories, ensuring code quality and adherence to requirements through executable scripts.

Core Features & Use Cases

AC Verification: Executes bash scripts to test specific Acceptance Criteria defined for a story.
Test Script Creation: Generates and maintains executable test scripts within the project's tests/manual/ directory.
Structured Reporting: Documents test results in a clear, parsable format for review and further action.
Use Case: After a developer marks implementation tasks as 'Done', this Skill runs predefined tests against the running application to confirm all ACs are met before proceeding to the next stage.

Quick Start

Execute the manual tests for story US-123 by running the command cd tests/manual && ./123-story-slug/test-story-slug.sh.

Frequently Asked Questions about ln-522-manual-tester

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

FAQPage Schema

How do I manually test Story Acceptance Criteria using bash scripts?▼

To manually test Story Acceptance Criteria, you execute bash scripts stored in the project's `tests/manual/` directory. These scripts validate specific ACs using bash and curl for API testing or puppeteer for UI testing.

How do I structure and run executable test suites for user stories?▼

Executable test suites are generated and maintained per user story within the `tests/manual/` directory. You run them by navigating to the specific story folder and executing its shell script, such as `./test-story-slug.sh`.

Can I use bash scripts to verify API and UI acceptance criteria?▼

Yes, bash scripts can verify API and UI acceptance criteria. The testing process utilizes bash and curl for API validation and puppeteer for UI testing to confirm that application behavior meets the defined requirements.

When should I run manual test scripts against my application?▼

You should run manual test scripts after a developer marks implementation tasks as Done. This verifies that all Acceptance Criteria are met against the running application before proceeding to the next development stage.

Does manual testing of acceptance criteria require external dependencies?▼

Manual testing of acceptance criteria using these bash scripts does not require external dependencies. The scripts rely on standard tools like bash, curl, and puppeteer to execute tests and validate application behavior.

How are manual test results documented and reported?▼

Manual test results are documented in a clear, parsable format for review and further action. The scripts save these findings to provide structured reporting on whether the Acceptance Criteria passed or failed.