ln-503-manual-tester

Generate executable bash/curl or puppeteer test scripts for Story AC verification.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-503-manual-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-503-manual-tester
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-503-manual-tester
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-503-manual-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Performs manual testing of Story AC via executable scripts, creating reusable test suites.

Core Features & Use Cases

  • Generates reusable test scripts in tests/manual/
  • Documents results in Linear with per-AC outcomes
  • Ensures regression readiness through scripted manual tests

Quick Start

Run the template-based manual test script for a StoryUS123.

Frequently Asked Questions about ln-503-manual-tester

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

FAQPage Schema
How do I automate manual testing of user story acceptance criteria?

Automate manual verification of Story AC by generating executable test scripts in bash/curl for APIs or Puppeteer for UI flows. The Skill creates reusable scripts stored in tests/manual/, executes them idempotently with Docker rebuilds, and reports pass/fail results to Linear.

Can I use Puppeteer to script UI regression tests for acceptance criteria?

Yes. Puppeteer scripts automate UI flow verification within the manual testing framework. The Skill generates per-story test scripts following templates, ensures idempotent execution, and captures outcomes as structured pass/fail matrices reported to Linear.

How do I create reusable test scripts that verify multiple acceptance criteria?

Use the script template system to generate per-story test scripts with config.sh for shared setup and individual AC verification steps. Scripts run idempotently in Docker containers, producing documented rerun commands and per-AC pass/fail results.

What's the best way to validate APIs and UI flows in an AC-driven project?

Combine bash/curl for API validation with Puppeteer for UI flows in executable test scripts. This mixed approach satisfies AC-driven checks, maintains regression readiness through scripted manual tests, and generates reusable test suites with Linear integration.

Do I need Docker to run manual test scripts for acceptance criteria?

Yes. The Skill requires mandatory Docker rebuilds before each test execution to ensure environment consistency. This supports idempotent script execution and reliable regression testing across your AC verification suite.

How are test results tracked when scripts verify story acceptance criteria?

Test execution produces structured pass/fail matrices with per-AC outcomes. Results are reported directly to Linear, creating documented records of manual verification alongside rerun commands for each test script.