skills.rest
kay6198835
kay6198835COMMUNITY
Explore all skills by this author →
GitHub

smoke-check

Automate critical path smoke tests and generate a PASS/FAIL report.

Updated Feb 8, 2024
Search Tags:#qa#reporting#sprint#test-automation#build-verification#smoke-check#platform-variants
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill smoke-check-kay6198835
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill smoke-check-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the critical path smoke tests to verify build readiness for QA and prevent hand-off of unstable builds.

Core Features & Use Cases

  • Automates the execution of the automated test suite and produces a PASS/FAIL report.
  • Supports sprint-scoped testing, optional platform targeting, and per-batch verification.
  • Generates a clear QA hand-off report for the testing team.

Quick Start

Run smoke-check to validate the current build and generate the PASS/FAIL report.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate smoke tests to verify build readiness for QA?▼

Automated smoke tests verify build readiness by executing the critical path test suite and aggregating results into a PASS/FAIL report, preventing the hand-off of unstable builds to the QA team.

Can I run sprint-scoped smoke tests across different platform variants?▼

Yes, sprint-scoped smoke tests support optional platform targeting and per-batch verification, allowing you to validate build readiness across specific platform variants during sprint completion scenarios.

What happens to smoke test execution when test runners are unavailable?▼

When test runners are unavailable, the smoke test process gracefully handles the missing runners to ensure the build verification workflow completes without blocking the QA hand-off reporting.

How do I generate a QA hand-off report after running automated build verification?▼

Generating a QA hand-off report involves running automated build verification, which executes the test suite and aggregates the results into a clear PASS or FAIL status document for the testing team.

Does automated smoke testing support phased batches for sprint completion?▼

Yes, automated smoke testing supports phased batches and per-batch verification, enabling progressive validation of sprint completion scenarios before final QA hand-off.

When do I need automated build verification instead of manual smoke testing?▼

Automated build verification is needed when you want to gate QA hand-offs at sprint completion, ensuring critical path execution and result aggregation prevent unstable builds from reaching manual testers.

Related Skills

Explore More Software Engineering Skills→
OneIdentityOneIdentity
24

testing-guide

Configure live Safeguard appliance access and run PowerShell 7 integration test suites.

Official
Advanced
GGPromptsGGPrompts
147

visual-qa

Run visual smoke checks and write PASS/FAIL results to .checkpoints/visual-qa.json.

Community
Basic
proffesor-for-testingproffesor-for-testing
436

test-reporting-analytics

Generate and index test reporting analytics for QE metrics in CI/CD pipelines.

Community
Advanced
Euraika-LabsEuraika-Labs
14

smoke-check

Run critical path smoke tests and produce a PASS/FAIL report.

Official
Advanced