VVarshainmanual-tester.hashnode.dev00The Test Summary Report — Saying "It's Ready!" 🏁Feb 24 · 3 min read · Welcome to Day 15—the final day of my 15-day Manual Testing journey! 🛠️🎉 We’ve analyzed requirements, designed plans, hunted bugs, and checked for regressions. Now, the big question remains: Is the Join discussion
VVarshainmanual-tester.hashnode.dev00Re-testing vs. Regression Testing — What's the Difference? 🔄Feb 23 · 2 min read · Welcome to Day 14 of my 15-day Manual Testing journey! 🛠️ Yesterday, we tracked the Bug Life Cycle. Once a developer says a bug is "Fixed," your job isn't over—it’s actually just beginning. Today, weJoin discussion
VVarshainmanual-tester.hashnode.dev00The Bug Life Cycle — From "New" to "Closed" 🔄Feb 22 · 3 min read · Welcome to Day 13 of my 15-day Manual Testing journey! 🛠️ Yesterday, we learned how to label bugs using Severity and Priority. But what happens after you click "Submit" on a bug report? It doesn't juJoin discussion
VVarshainmanual-tester.hashnode.dev00Severity vs. Priority — Sorting the Emergencies 🚦Feb 21 · 3 min read · Welcome to Day 12 of my 15-day Manual Testing journey! 🛠️ You’ve found a bug—congratulations! But now comes the hard part: How do you explain how bad it is? Not every bug is a disaster, and not everyJoin discussion
VVarshainmanual-tester.hashnode.dev00Error Guessing The "Detective" Technique 🕵️♂️Feb 20 · 3 min read · Welcome to Day 11 of my 15-day Manual Testing journey! 🛠️ For the last two days, we’ve used math-based techniques like BVA and ECP. But sometimes, bugs don't follow a range—they follow human behaviorJoin discussion