testing-user-stories-validation

Name: testing-user-stories-validation
Availability: InStock
Author: pelchers

Automate end-to-end user story validation with Playwright and capture evidence.

Updated Mar 1, 2026

Search Tags:#playwright #validate #user-stories #qa-automation #end-to-end-testing #evidence-capture #test-documentation

Ready to run

npx skills add https://github.com/pelchers/SessionSaver --skill testing-user-stories-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-user-stories-validation
Source: https://github.com/pelchers/SessionSaver/tree/main/.codex/skills/testing-user-stories-validation
Command: npx skills add https://github.com/pelchers/SessionSaver --skill testing-user-stories-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates all user stories end-to-end using Playwright, capturing evidence and documenting validation steps to reduce manual QA effort.

Core Features & Use Cases

End-to-end testing of all user stories with Playwright to verify acceptance criteria.
Automatic screenshot capture at key validation steps to build a traceable audit trail.
Structured documentation: per-story folders with story.md and a validation/ subfolder, plus a master list to track progress.

Quick Start

Run Playwright tests for every user story, record results, and update the master list accordingly.

Frequently Asked Questions about testing-user-stories-validation

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

FAQPage Schema

How do I automate end-to-end user story validation with Playwright?▼

Automate end-to-end user story validation by running Playwright tests that verify acceptance criteria against the web UI. This captures validation evidence and generates structured documentation, reducing manual QA effort while ensuring reproducible test execution.

Can I capture screenshots automatically during Playwright QA automation?▼

Yes, automatic screenshot capture occurs at key validation steps during Playwright QA automation. This builds a traceable audit trail by saving visual evidence within structured per-story documentation folders for comprehensive test tracking.

What is the best way to document test evidence for user stories?▼

Document test evidence for user stories by creating structured per-story folders containing a story.md file and a validation subfolder. A master list tracks overall progress, ensuring reproducible test execution and step documentation across the project.

How do I verify acceptance criteria across web UI user stories?▼

Verify acceptance criteria across web UI user stories by executing automated end-to-end tests with Playwright. This validates each story's requirements systematically and records the results in a master list with corresponding evidence capture.

Do I need Playwright installed to run end-to-end user story validation?▼

Yes, Playwright is required as the underlying engine to execute end-to-end testing and interact with the web UI. The validation process relies on Playwright to verify acceptance criteria and capture screenshots for evidence.

Why does user story validation require structured folders and a master list?▼

Structured folders and a master list are required to organize captured evidence and track validation progress reproducibly. This structure ensures every user story has dedicated documentation, making QA automation results traceable and auditable.

Spectra29115

testing

Execute automated end-to-end UI tests with Playwright and capture screenshots.

Community

Intermediate

studiochat

data-expert

Analyze Studio Chat API data to generate JSON or CSV analytics reports.

Official

Advanced

sunholo-data

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official

Intermediate