smoke-test

Run API and UI smoke tests to verify the Everruns system works correctly. Use this skill when you need to test system functionality after changes, verify deployments, or troubleshoot issues. Supports both Docker-based and no-Docker environments.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill automates the execution of API and UI smoke tests for the Everruns system, ensuring core functionalities are operational after code changes or deployments. It streamlines system health checks, integration testing, and troubleshooting across both Docker and local environments, providing a robust safety net for developers and QA engineers.

Use Cases

  • Post-Deployment Verification: Automatically run a suite of health checks and API tests immediately after a new deployment to ensure the production or staging environment is stable and reachable.
  • Continuous Integration Support: Execute unit and integration tests locally using cargo to catch regressions in the durable engine or core logic before pushing code to the repository.
  • System Troubleshooting: Quickly diagnose connectivity or service issues by checking API ports (9000) and UI ports (9100) and inspecting logs to identify failures in the Everruns stack.
  • Environment Readiness Check: Verify that the local development environment is correctly configured with all necessary services (PostgreSQL, API, UI) running before starting feature development.
namesmoke-test
descriptionRun smoke tests to verify the Everruns system works correctly.

Smoke Tests

Verify the system is working after changes.

Quick Start

# Start server (no Docker needed, --no-watch for faster startup)
just start-dev --no-watch

# Run tests
cargo test

Checklist

1. Start Server

just start-dev --no-watch  # In-memory, no Docker, fast startup
# or: just start-all --no-watch  # With PostgreSQL persistence

2. Health Check

curl -s http://localhost:9000/health | jq
# Expected: {"status": "ok", ...}

3. Run Tests

# Unit + integration tests
cargo test

# Durable engine tests
cargo test -p everruns-durable --lib

4. UI Check

curl -s -o /dev/null -w "%{http_code}" http://localhost:9100
# Expected: 200 or 307

5. API Endpoint Test

ORG="org_00000000000000000000000000000001"

# Create agent
curl -s -X POST "http://localhost:9000/v1/orgs/$ORG/agents" \
  -H "Content-Type: application/json" \
  -d '{"name": "Test", "system_prompt": "You are helpful."}' | jq '.id'

Full API Reference

See http://localhost:9000/swagger-ui/ for complete API documentation.

Troubleshooting

# Check ports
lsof -i :9000  # API
lsof -i :9100  # UI

# View logs (DEV MODE runs in foreground)
# Ctrl+C to stop, then restart with: just start-dev