compartment-smoke-test

To run an e2e smoke test for a local stack, boot the Compartment deployment, log in via automated browser interactions, deploy fixtures, and validate protected routes. This ensures stack health and verifies real-user flows end-to-end.

Browser-based smoke testing validates protected routes by automating login and logout flows through a real browser interface. It verifies that authentication guardrails and local stack health checks function correctly from a user perspective.

Yes, you can automate CLI status checks and fixture deployment in a local environment. The smoke test orchestrates these tasks alongside browser interactions to provide comprehensive end-to-end validation of the deployment.

Local stack smoke testing can delegate automated browser interactions to a dedicated browser subagent when policy allows. This enables real-user flow validation while maintaining coordinated CLI checks and guardrail validations.

Automated browser smoke tests for local deployments are limited to validating stack health, fixture deployment, and protected route access. They focus on end-to-end validation scenarios rather than comprehensive performance or load testing.