How do you run a smoke test after deployment?

How do you run a smoke test after deployment?

A smoke test checks whether the essential deployed paths are functioning. It should be short, intentional, and easy to repeat after a release.

Choose critical actions

Load the application over its production domain, authenticate with an intended test account, create a small project, and run a short generation. Retrieve the stored result and verify basic playback and captions where applicable. Check that job status remains available after reload. Avoid publishing externally unless that action is deliberately part of the approved test.

Interpret results narrowly

Record the deployment version and observed result. Inspect logs for unexpected failures or repeated attempts. Clean up identifiable test artifacts according to the project’s retention policy. A passing smoke test confirms those specific paths, not all workloads or account types. If it fails, pause expansion of traffic or features while diagnosing the failing boundary.