Generate, execute, and track feature test scenarios with pass rate tracking.
npx skills add https://github.com/s0613/S-skills --skill test-scenario-s0613
Please help me install this Agent Skill. Skill: test-scenario Source: https://github.com/s0613/S-skills/tree/main/test-scenario Command: npx skills add https://github.com/s0613/S-skills --skill test-scenario-s0613
Manually creating structured test scenarios, tracking execution results, identifying failure root causes, and iterating to improve feature pass rates is time-consuming, disorganized, and makes it hard to measure progress over time.
Use the /test-scenario command to start a new test cycle for your product features, paste Chrome extension test results into the chat to log outcomes, and repeat cycles until your target pass rate is reached.
High-intent search queries and answers about installing and using this skill.
Automating test scenario creation involves generating structured prompts with preconditions, steps, and pass/fail criteria, then executing them via a Chrome extension and parsing the results to track pass rates iteratively.
Cycle-based iterative testing works by running test scenarios, parsing structured result blocks, logging failure root causes, and repeating cycles until a target pass rate is reached, tracking progress in state files.
Yes, you can analyze failure root causes by parsing Chrome extension test execution results, evaluating pass status per step, and generating prioritized fix suggestions for failed items.
Yes, you need a Chrome extension integration for test execution. The workflow requires pasting structured test result blocks from the extension into the chat to evaluate outcomes and log pass rates.
The best way to track pass rate improvement is by maintaining an improvement log for failed items and state files for cycle tracking, automatically signaling completion when your target pass rate is met.
Limitations include dependency on Chrome extension test execution formats and structured result parsing; it specifically targets browser-based feature tests rather than API or unit testing workflows.
JosephAnsonGenerate QA test documentation from Linear issues and git commits.
mvillmowGenerate prioritized remediation steps with code snippets from error logs.
cenconq25Parse CI run histories to compute per-test pass rates and maintain a flaky-test registry.
lidge-junGuide web application testing with Playwright browser automation and coverage analysis.
