Manual Testing - The "What" and "WHY"
Welcome to Day 1 of my 15-day journey into the world of Software Testing!
Today, we are stripping everything back to the basics. Before we touch automation or complex tools, we have to understand the core — Manual Testing.
🛑 The "What" (The Definition)
Think of Manual Testing as a Safety Inspection.
The Manual Part: No scripts, no code, just a human and the app.
The Goal: Finding the gap between "What it should do" vs. "What it actually does."
💡 The "Why" (The Cheat Code)
Why not just automate everything? Because machines follow instructions, but Humans find bugs.
The "Eye" Test: A script can check if a button exists; only a human can see it’s an ugly shade of neon pink that hurts the eyes.
The "Chaos" Factor: Humans click randomly, lose internet connection, and do things developers didn't expect.
The "Vibe" Check: Automation doesn't understand "user-friendly."
🧠 Memory Hook: The 2-Minute Comparison
| Feature | Automated Testing | Manual Testing |
| Speed | Fast ⚡ | Slower 🐢 |
| Best For | Repeatable tasks (Regression) | New features & UX |
| Intuition | Zero (Logic only) | High (Human gut feeling) |
| Cost | High (Setup time) | Low (Start immediately) |
🚀 Pro-Tip for New Testers
Manual Testing is not "clicking around." It is a structured investigation.
Step 1: Read the requirement.
Step 2: Predict how it could break.
Step 3: Try to break it.
Today’s Takeaway: Manual testing is the foundation. You can’t automate a process you don't understand manually.
Tomorrow: We tackle the "V brothers"—Verification vs. Validation. See you there!
💬 Let’s Chat!
What was the first "bug" you ever found in an app?
Was it a broken button, a strange typo, or a complete crash? Share your story in the comments—let's see who found the funniest one! 👇