Why Smoke testing and sanity testing in Testing Fundamentals? - Purpose & Use Cases

The Big Idea

What if you could catch big app problems in just minutes instead of hours?

The Scenario

Imagine you just got a new phone app update. You try opening the app and clicking a few buttons to see if it works. But you only check a couple of things, and miss some big problems hidden inside.

The Problem

Checking everything by hand takes too long and is tiring. You might forget to test important parts or make mistakes. This can let bugs slip through and cause unhappy users.

The Solution

Smoke testing and sanity testing help by quickly checking the most important parts first. Smoke testing makes sure the app starts and runs basic features. Sanity testing checks if recent fixes work well. This saves time and catches big problems early.

Before vs After

✗ Before

Open app, click buttons, watch for errors, repeat for many features

✓ After

Run smoke test suite to check main features; run sanity tests after fixes

What It Enables

It lets teams find major issues fast and decide if deeper testing is worth doing.

Real Life Example

Before releasing a new app version, testers run smoke tests to confirm the app launches and key screens load. After fixing a bug, they run sanity tests to check that bug is really fixed without breaking other parts.

Key Takeaways

Manual checks are slow and easy to miss bugs.

Smoke testing quickly checks main functions.

Sanity testing verifies recent fixes work correctly.