Software QA Engineer and mentor Anastasia Dyka drew the attention of QA specialists to the fact that context often decides everything. According to her, sometimes what seems wrong is actually not. Here are examples of such behavior that can be useful even for experienced testers.
Software QA Engineer and mentor Anastasia Dyka drew the attention of QA specialists to the fact that context often decides everything. According to her, sometimes what seems wrong is actually not. Here are examples of such behavior that can be useful even for experienced testers.
«Being a good QA is not just about finding bugs. It’s about the ability to understand the system’s intentions, to see the bigger picture,» emphasizes Anastasia Dyka, adding that the key question in this process is «What exactly did you expect?»
Here are her examples of «bugs» that are actually features:
On small screens, elements are deliberately shifted down so as not to interfere with reading.
Conclusion: this is a UX decision, not a mistake.
The product focuses on a fast flow without unnecessary popups.
For example, adding to «Favorites» simply changes the icon / is highlighted in a different color.
Conclusion: there is a visual indicator, which means everything is working.
In financial, medical, or legal products, data may be immutable.
Conclusion: this is not a defect, but a business rule.
Tip: Always check what the system allows before filing a bug.
Systems often start for one country, where naming requirements are different.
Conclusion: This is not a bug, but an ongoing validation.
Write as an improvement, not as a defect.
To avoid double payment or creating multiple applications, the button is blocked.
Conclusion: This is a UX decision for security reasons.
Check: is there a loading indicator or does the button become inactive?
