smoke-test

Validate Docker, database, and web/API availability for FastAPI deployments.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/michaelayoade/dotmac_crm --skill smoke-test-michaelayoade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/michaelayoade/dotmac_crm/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/michaelayoade/dotmac_crm --skill smoke-test-michaelayoade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of shipping broken deployments by verifying that Docker services, the database, and the web UI/API all work together before users hit issues.

Core Features & Use Cases

  • Stack health validation with Docker MCP: Confirms key containers are running and healthy, including the FastAPI app, PostgreSQL/PostGIS, Redis, and Celery components.
  • Database sanity checks via DB MCP: Ensures core tables contain expected data and that recent activity timestamps update.
  • Application and API verification with Playwright MCP: Checks the /health endpoint, completes the login flow, loads critical admin pages, optionally validates HTMX inbox partials, and verifies API endpoints return expected responses.

Quick Start

Run the smoke-test skill to verify container health, database queries, and critical Playwright UI/API paths for the current deployment.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I run a smoke test to verify Docker, database, and API availability after deployment?

A smoke test validates end-to-end application availability by checking Docker container health, database row counts and recency, Playwright browser navigation with console error validation, and API endpoint responses for deployment verification and regression detection.

How does Playwright browser testing validate FastAPI admin UI and HTMX inbox partials?

Playwright validates the FastAPI admin UI by completing the login flow, loading critical admin pages, optionally validating HTMX inbox partials, and capturing browser console errors to verify web surface availability and regression.

Can I use this smoke testing approach to check PostgreSQL database health and recent activity timestamps?

Yes, the smoke test performs database sanity checks via DB MCP to ensure core PostgreSQL tables contain expected row counts and that recent activity timestamps update properly before passing the stack health validation.

What is the best way to catch end-to-end stack breakages across Docker containers and API endpoints?

The best way to catch stack breakages end-to-end is running an integrated smoke test that requires successful Docker container health checks for FastAPI and PostGIS, database sanity queries, and Playwright API endpoint response validation for pass/fail reporting.

Does smoke testing work with Docker MCP to confirm FastAPI, Redis, and Celery containers are healthy?

Yes, stack health validation uses Docker MCP to confirm key containers including the FastAPI app, PostgreSQL/PostGIS, Redis, and Celery components are running and healthy before proceeding to database and web UI checks.

What are the limitations of using a smoke test for regression detection versus full end-to-end testing?

A smoke test for regression detection is limited to verifying critical availability paths like the API login flow, data retrieval endpoints, and container health, rather than validating comprehensive business logic, edge cases, or performance benchmarks.