Name an example of a situation where there might be multiple smoke tests.

In a large multi-module application or with different environments (e.g., Production, Staging, Dev). Examples of situations: 1. Multi-module application: a. A separate smoke test for the authorization module (login/logout). b. A separate smoke test for the profile management module (editing data). c. A separate smoke test for the order placement module (adding to cart, proceeding to payment). Tests are run in parallel or sequentially, verifying the basic operability of each key module after deployment. 2. Different environments: a. Smoke test for Production: checking critical functions on the 'live' server (e.g., homepage availability, login ability). b. Smoke test for Staging: more detailed check of basic functions before release to Production. c. Smoke test for Dev: quick check after each build on the test environment. In each case, several smoke tests are needed to quickly determine whether the system's key parts or environment are functioning after changes/deployments.