test-hardening

Convert QA Contract criteria into Jest, Storybook, and Playwright regression tests.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill test-hardening
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-hardening
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/test-hardening
Command: npx skills add https://github.com/WellApp-ai/Well --skill test-hardening

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert verified QA Contract criteria (G#N, AC#N) into permanent automated tests. Ensures passing scenarios become regression tests.

Core Features & Use Cases

  • Automates transforming QA verification results into backend, UI, and E2E tests.
  • Generates test skeletons for Jest, Storybook, and Playwright based on criteria.
  • Supports quick hardening by producing ready-to-run templates from verification reports.

Quick Start

Run after qa-commit GREEN verdict to produce regression tests from the latest Verification Report.

Frequently Asked Questions about test-hardening

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

FAQPage Schema
How do I generate automated regression tests from QA verification criteria?

Generating automated regression tests from QA criteria involves converting verified G#N and AC#N contract items into permanent test suites. This Skill transforms those passing verification scenarios into Jest, Storybook, and Playwright test skeletons to prevent future functional regressions.

Can I create Playwright e2e and Jest backend tests from the same verification report?

Yes, you can create Playwright e2e and Jest backend tests from the same report. The conversion process reads your verified QA Contract criteria and outputs backend test skeletons, Storybook UI states, and Playwright end-to-end files simultaneously for comprehensive test coverage.

How do I harden Storybook UI states against regressions after a QA review?

Hardening Storybook UI states against regressions requires translating verified acceptance criteria into static Storybook stories. This process generates ready-to-run story templates from your verification report, locking in visual and functional states to catch UI defects in future builds.

Do I need a passing qa-commit GREEN verdict to start automating regression tests?

Yes, you need a passing qa-commit GREEN verdict to start automating regression tests. The process runs after this verification step, using the latest Verification Report to ensure only confirmed and passing scenarios are converted into permanent automated test suites.

What is the best way to prevent code regressions after passing QA acceptance criteria?

Preventing code regressions after passing QA acceptance criteria is best achieved by automating test hardening. Converting verified G#N and AC#N criteria into Jest, Storybook, and Playwright test files ensures that any future code changes breaking these scenarios are automatically caught during CI.

Are generated test skeletons ready to run immediately without manual integration?

Generated test skeletons require manual integration despite including templates and references. The outputs provide foundational Jest, Storybook, and Playwright test structures derived from QA criteria, which developers must then connect to existing application code and CI pipelines for execution.