What Is Manual Testing? Think Like a User, Prove Like QA

What you can learn on this page

• 1. Manual testing = experiencing the product like a user — Imagine buying a coffee machine. You do not just press the button — you check what happens when water runs out, when there is no cup, when coffee overflows. But here is the key question: why is "does the button work?" not enough? Because the user alr
• 2. Test case = a small experiment with proof — A doctor does not order a vague test — the specific panel, sample type, and expected reference range are all written down. A test case works the same way: every run must produce the same experiment. Here is the key question: why is "log in and check"
• 3. Exploratory testing = navigating with a map, not by memorizing — The first time you enter a shopping mall, you do not have a pre-written script for every store — but you are not wandering randomly either. You form a mental map: where is the exit, is there an elevator, which floor has food? The thought-provoking question her
• 4. Bug report = a recipe that lets the team reproduce the failure — When your car breaks down, telling the mechanic "it does not work" leads to guesswork and wasted time. But saying "yesterday morning in the cold, at 80 km/h, the front right started vibrating and the engine light came on" immediately narrow
• 5. Severity = the impact of a defect on users and business flow — In a restaurant, missing salt is annoying — but a broken fire alarm is life-critical. Both are problems, but they demand completely different response times and resources. The thought-provoking question here is: "Why should QA classify bugs at all — is no
• 6. Regression testing = proving old behavior still works — After fixing a leaky faucet, you do not just check the new washer — you also check for drips under the sink, run the hot water, and make sure the drain still flows. The key question to ask yourself: "We only changed that one part, why check everything els