143

Receiving a bug report from the manual tester “numeric input does not work”.

He accidentally disabled Num Lock on his keyboard.

Comments
  • 12
    User education required
  • 17
    Too be fair... That's stumped me before.

    (Only for like 30 seconds lmao. I'm stupid, but not that stupid)
  • 8
    Fucking QA people, man. And I wouldn't even be mad about mistakes like those, it's their fucking arrogance when reporting "defects" what unnerves me.
  • 2
    Honestly, I find these are quite common mistakes and usually you can have a good laugh about it after you figure it out. Unless ofc you get stuff like this reported 3> times a day. Then I feel like choking the person. Even tho its just honest mistakes and everyone has the right to be tired from time to time
  • 1
    You can't check for the states beforehand in JavaScript(Browser sandbox) for example, but you might have some key input feedback nonetheless, to maybe show a warning until a numerical value was set.
  • 1
  • 3
    😂😂😂 I’m adding that to my “tech support” repertoire
  • 0
    @Hazarth we had a good laugh though.
  • 4
    I used to get reports about a bug not fixed and the QA guy forgot to update the app T_T
  • 0
    Do you have Permanent in this company? No... you are fired ! And keep the broken keyboard i dont need it here !!! xX
  • 0
  • 2
    Test your Tester first 😂
  • 0
    Test your Tester first 😂
  • 0
    🤣🤣
  • 0
    If it’s an input field, you could use something like yup for type validation and error handling (in JavaScript). I admit that it’s annoying when someone puts forward a bug report and they haven’t done their due diligence to ensure it’s not user error on their end. Though sometimes the fact that there’s room for user error can be enlightening re: UX Design.
  • 1
    @Stuxnet I am adopting that as my new motto.

    I am stupid but not that stupid
Add Comment