For Example : Need to test login > view balance and deadline is 4 hours.
When you enter username, password and click login then browser shows nothings or errors . Developers needs 5 hours to solve this and the other modules become stacks for this module. In this situation is very common and risky for development and time consume.
Solution: Smoke / Sanity testing can solve this.
- This is used to check critical functionalities of the systems before it is accepted for major testing.
- Sanity testing is quick and non-exhuastive.
- Goal is not to find defects but to check health.
Image comes from google search https://www.bytelion.com/smoke-testing-vs-regression-testing/