Smoke Testing

Included with Lifetime

$97 forever

Health endpoint and critical path smoke testing patterns. Use when running quick validation tests, checking health endpoints, verifying critical paths respond correctly, or when user mentions smoke testing, health checks, quick validation, sanity checks.

Generalscripts

What this skill does


# Smoke Testing

**CRITICAL: The description field above controls when Claude auto-loads this skill.**

## Overview

Provides scripts, templates, and patterns for smoke testing - quick validation that critical endpoints and pages are responding correctly before running full test suites.

## Instructions

### 1. What is Smoke Testing?

Smoke tests are the fastest, most basic tests that verify:
- The application starts and responds
- Health check endpoints return 200
- Critical user-facing pages load without errors
- Key API endpoints are reachable

They run before unit/integration/E2E tests to catch deployment failures early.

### 2. Running Smoke Tests

**Full smoke test orchestrator:**
```bash
bash scripts/run-smoke-tests.sh [base-url] [project-path]
```

**Individual checks:**
```bash
bash scripts/check-health-endpoint.sh [health-url]
bash scripts/verify-critical-paths.sh [base-url] [paths-file]
```

### 3. Configuration

Smoke test configuration lives in `.claude/project.json`:
```json
{
  "testing": {
    "smoke": {
      "health_endpoint": "/api/health",
      "critical_paths": ["/", "/login", "/dashboard"],
      "base_url": "http://localhost:3000",
      "timeout_seconds": 10
    }
  }
}
```

Or use a standalone config file:
```json
// smoke-test-config.json
{
  "base_url": "http://localhost:3000",
  "health_endpoint": "/api/health",
  "timeout_seconds": 10,
  "critical_paths": [
    { "path": "/", "expected_status": 200 },
    { "path": "/login", "expected_status": 200 },
    { "path": "/api/health", "expected_status": 200, "expected_body": "ok" }
  ]
}
```

### 4. Health Check Endpoint Patterns

**Next.js App Router:**
```typescript
// src/app/api/health/route.ts
export async function GET() {
  return Response.json({ status: 'ok', timestamp: new Date().toISOString() })
}
```

**Express:**
```javascript
app.get('/health', (req, res) => {
  res.json({ status: 'ok' })
})
```

**FastAPI:**
```python
@app.get("/health")
async def health():
    return {"status": "ok"}
```

**Go:**
```go
http.HandleFunc("/health", func(w http.ResponseWriter, r *http.Request) {
    w.WriteHeader(http.StatusOK)
    json.NewEncoder(w).Encode(map[string]string{"status": "ok"})
})
```

### 5. CI/CD Integration

Smoke tests should run:
- After deployment to verify the deploy succeeded
- Before E2E tests as a gating check
- On every PR as a quick validation

## Available Scripts

1. **run-smoke-tests.sh** - Orchestrator that runs all smoke checks
2. **check-health-endpoint.sh** - Hit a health endpoint and verify response
3. **verify-critical-paths.sh** - Verify critical pages respond with 200

## Available Templates

1. **smoke-test-config.json** - Configuration file template
2. **health-check-test.sh** - Reusable health check function

## Available Examples

1. **basic-smoke-test.md** - Simple health check smoke test
2. **critical-path-smoke.md** - Testing critical user paths
3. **ci-smoke-integration.md** - Adding smoke tests to CI pipeline

## Requirements

- `curl` for HTTP requests
- `jq` for JSON parsing (optional)
- Running application server (or ability to start one)

Files: 9

Size: 12.7 KB

Complexity: 42/100

Category: General

Source: https://github.com/vanman2024/dev-lifecycle-marketplace/tree/main/plugins/testing/skills/smoke-testing

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts