Skip to main content

Test Your Infrastructure After Deployment

· 2 min read
Erik Osterman
Founder @ Cloud Posse

A successful deployment still needs checks that the application is healthy. Running those checks as ordinary commands can bury failures in successful logs or stop before the remaining tests run. The new test step collects the results, keeps passing output quiet, and reveals each failed check's logs.

Post-deployment tests
 
00:00.0 / 00:00.0

View the full example

The Problem

Post-deployment checks need a clear result for every test, including independent checks that can still run after another fails. Shell wrappers and CI-specific reporting make that behavior harder to reuse locally and across deployments.

The Fix

Atmos supports type: test in workflows, custom commands, and lifecycle hooks. Tests continue by default, while a tree with green/red dots and a bottom progress bar shows the results. Nested parallel and matrix groups share the same report.

How to Use It

Attach a test step to an after.terraform.apply hook with kind: step and on_failure: fail to make checks part of the deployment result. Use output: all when debugging, or fail.mode: fail_fast when remaining checks should stop after an error. CI receives a static tree with the same failure details.

See the test step reference for configuration and failure behavior.

The local example runs without stacks. Running bare atmos now displays usage and available commands, including custom commands, without requiring stack configuration.

Get Involved

Try the local example and share feedback in GitHub Discussions.