A bug is anything that would make a user think less of your product. It’s the simple. You can split hairs from there, but that’s the baseline. In this post, we’ll talk about what a bug is and how you should approach finding and reporting them.
If we define a bug as anything that detracts from your product, that doesn’t mean we can leave it at that. These bugs can be categorized in many ways, but the most logical to me, is to consider what type of defect it is and how exactly it fails a user. I’m always looking for ways to expand my empathy for the users I expect to use my product, and this type of categorization helps.
With that in mind, these are the ways I sort out bugs.
Functionality bugs fail a user because we’re violating the stated goals of our product.
This is the baseline for bugs for an average tester. Any one who tests software should be ready to ask questions about requirements and be ready the moment a new feature is available to test with both standard and tricky use cases.