rembric-smoke-tests

End-to-end smoke tests for local Docker compose dev stack changes require bringing up the stack, verifying source mounts, checking container health, probing changed surfaces, and tearing down. This standardized workflow eliminates manual verification of integrated functionality.

MCP tool testing fails on SSE-framed responses because standard parsing logic breaks on the server-sent events format. This smoke testing workflow includes built-in guardrails to explicitly handle SSE-framed MCP responses during surface probing.

Verifying HTTP API routes and database migrations before a pull request is best handled by a standardized smoke testing workflow. It probes changed surfaces across the local development stack to catch integration issues early and eliminate error-prone manual checks.

Resolving global Docker Compose project name conflicts during dev stack bring-up requires explicit checks for conflicting project names. This smoke testing workflow includes built-in pitfall guardrails to detect and account for global compose project conflicts before validation.

Integration testing on rembric codebase modifications requires Docker Compose to bring up the local development stack. The standardized workflow validates source mounts, checks container health, and probes changed surfaces across the integrated environment before teardown.

Smoke testing blocked .env access in containers is handled by built-in pitfall guardrails that account for common dev environment issues. The workflow explicitly checks for blocked .env access during stack bring-up to prevent false negatives during health validation.