Why is smoke testing on production after release necessary and is it correct?

Smoke tests on production after release are needed for a quick check of the main application functions in real conditions. This allows ensuring that critical parts of the system work correctly after deployment and that there are no serious failures.

Whether this is correct depends on the context. Ideally, smoke tests should be performed during testing and staging to minimize risks on production. However, in some cases, especially with continuous deployment, automated smoke tests on production help quickly identify problems and respond promptly.

It is important that such tests are as fast as possible and do not affect performance or user experience. It is also advisable to have monitoring and alerts so that in case of smoke test failures, the team can quickly take action.