testing-smoke

Execute minimal automated tests to verify critical application functionality and environment stability.

4|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wojons/skills --skill testing-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-smoke
Source: https://github.com/wojons/skills/tree/main/skills/testing-smoke
Command: npx skills add https://github.com/wojons/skills --skill testing-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a rapid way to confirm that an application's most critical functions are operational after changes or deployments, preventing deeper issues from going unnoticed.

Core Features & Use Cases

  • Rapid Validation: Checks essential services like application startup, database connectivity, and authentication.
  • Pre-Testing Gate: Ensures basic stability before initiating more time-consuming integration or end-to-end tests.
  • Use Case: After deploying a new version of your web application, run this skill to confirm the server is running, users can log in, and the main API endpoint is responsive.

Quick Start

Run the smoke tests for the production environment.

Frequently Asked Questions about testing-smoke

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

FAQPage Schema
What is a smoke test and when do I need to run one after deployment?

A smoke test verifies critical application functionality and environment stability after changes. You need to run it after deployment to confirm service availability, database reachability, and core API responsiveness before deeper testing phases.

How do I verify core application health and database connectivity before running integration tests?

Verify core application health by executing a minimal set of automated tests targeting service availability, database connectivity, and authentication. This ensures basic operational integrity and acts as a pre-testing gate before time-consuming integration tests.

Can I use smoke tests to check API responsiveness and service availability in a production environment?

Yes, you can use smoke tests to check API responsiveness and service availability in a production environment. They rapidly validate critical functions like server status and user login to ensure the deployment is stable.

What is the best way to validate critical application functionality without running time-consuming end-to-end tests?

The best way to validate critical functionality without end-to-end tests is running a rapid smoke test. It checks essential services like application startup and core API endpoints, preventing deeper issues from going unnoticed while saving testing time.

Does smoke testing require any dependencies or specific CI/CD pipeline configuration?

Smoke testing requires no dependencies or specific CI/CD pipeline configuration. It operates independently using scripts and references to validate basic environment stability and application startup.

Why should I run a smoke test instead of immediately starting comprehensive testing after a deployment?

You should run a smoke test before comprehensive testing because it provides rapid validation of critical functions, preventing deeper issues from going unnoticed and ensuring basic stability before investing time in integration or end-to-end tests.