skills.rest
jayhjenkins
jayhjenkinsCOMMUNITY
Explore all skills by this author →
GitHub

Jay-Dev QA Testing Skill

Automate three-tier QA testing with TEST_INDEX.md and RUNS/ reports.

Updated Jan 3, 2026
Search Tags:#regression#smoke-tests#qa-testing#sanity-tests#test-index#RUNS
One-click install
npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill jay-dev-qa-testing-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Jay-Dev QA Testing Skill
Source: https://github.com/jayhjenkins/Dev-Team-Full-SDLC/tree/main/.claude/skills/jay-dev-qa-testing
Command: npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill jay-dev-qa-testing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Jay-Dev QA Testing Skill provides a structured approach to validating software quality by implementing three-tier QA: smoke, sanity, and regression testing, ensuring changes don't regress existing functionality.

Core Features & Use Cases

  • Three-tier QA methodology: smoke, sanity, and regression tests to cover quick checks, feature validation, and end-to-end workflows.
  • Test-index driven: relies on docs/qa/TEST_INDEX.md to organize test cases, checklists, and evidence.
  • Shipping readiness: supports pre-release verification and audit trails through RUNS/ reports.

Quick Start

  • Inspect docs/qa/TEST_INDEX.md to understand current tests
  • Run smoke tests for UI changes using the prescribed commands or toolchain
  • Create a QA run report in docs/qa/RUNS/ to document results

Frequently Asked Questions about Jay-Dev QA Testing Skill

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

FAQPage Schema
How do I automate regression testing for web applications before shipping?▼

Regression testing for web applications is automated by standardizing a three-tier QA process that validates completed feature slices and generates pre-shipping audit trails in RUNS/ reports.

What is the difference between smoke, sanity, and regression tests?▼

Smoke tests perform quick UI checks, sanity tests validate completed feature slices, and regression tests execute end-to-end workflows to ensure new changes do not regress existing functionality across the codebase.

How do I create a test index for QA test planning and traceability?▼

A test index for QA test planning is created using docs/qa/TEST_INDEX.md to organize test cases, checklists, and evidence, ensuring traceable quality gates across the software development lifecycle.

Do I need a specific test framework to run smoke tests for UI changes?▼

No specific test framework dependency is required; the skill applies prescribed commands or toolchains to run smoke tests for UI-affecting changes using the standardized test index methodology.

What's the best way to document QA run reports for audit trails?▼

Documenting QA run reports for audit trails is done by creating files in docs/qa/RUNS/ to record run results, supporting pre-release verification and traceable quality gates for software changes.

When should I run sanity tests instead of full regression tests?▼

Sanity tests should be run to validate completed feature slices, whereas regression tests are reserved for pre-shipping validation to ensure broader end-to-end workflows remain unaffected.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

testing-checklist

Generate smoke, sanity, and regression testing checklists from input requirements.

Community
Basic
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
cin12211cin12211
218

playwright-expert

Automate cross-browser end-to-end tests with Playwright and Node.js.

Community
Intermediate
apacheapache
175

manage-tests

Define and execute OFBiz automated test suites via XML and Gradle.

Official
Intermediate