The bugs shared in this section were originally posted in the LinkedIn group “Bee-ing a QA Tester.” They are real issues I discovered during my experience working as a QA tester, through exploratory testing, automation testing, and everyday interaction with applications. Each one reflects a small lesson about usability, data integrity, or system behavior that can easily be overlooked.
- Bug #001 Bee-ing a QATester: I found a bug… honey! – “Contact Form Accepts Empty Message with Spaces”
- Bug #002 Bee-ing a QATester: I found a bug… honey! The Day the Dropdown Ghosted My Country. A bug Found During my Selenium Romance.
- Bug #003 Bee-ing a QATester I found a bug… honey! Mission Accomplished… But Nobody Told the User
- Bug #004 Bee-ing a QATester: I found a bug… honey! I found a bug… honey! Float Hopes, Integer Storage . A Love Story Gone Truncated.
- Bug #005 Bee-ing a QATester: I found a bug… honey! I found a bug ..honey! The Printer with Short-Term Memory Loss
- Bug #006 Bee-ing a QATester: I found a bug… honey! I found a bug ..Honey! . “I’m Everywhere: The Omnipresent User Bug”
- Bug #007 Bee-ing a QATester: I found a bug… honey! I found a bug ..honey! . “Timezone Tango: When Data Dances to the Server’s Clock”
- Bug #008 Bee-ing a QATester: I found a bug… honey! “Lost in URL Land: Users Pick Their Own Endpoints”
- Bug #009 Bee-ing a QATester: I found a bug… honey! “The Lazy Cart Counter”
- Bug #10 Bee-ing a QATester: I found a bug… honey! “Caught in the Act: Spaces Sabotaging My Data”
- Bug #11 Bee-ing a QATester: I found a bug… honey! “When Placeholder Plays Boss”
- Bug #12 Bee-ing a QATester: I found a bug… honey! “The Logout That Runs on Its Own Clock”
- Bug #13 Bee-ing a QATester: I found a bug… honey! “Tab Key: Mission Impossible”
- Bug #14 Bee-ing a QATester: I found a bug… honey! “Device Knows Me, App Doesn’t”
- Bug #15 Bee-ing a QATester: I found a bug… honey! “Autocomplete: Security Loophole”