Editor’s Note: The relationship between programmers and software testers needs no introduction. These classic responses, compiled and shared by developers abroad, are “universally applicable.”
20. “That’s weird…” That’s weird…
19. “It’s never done that before.” It’s never done that before.
18. “It worked yesterday.” It worked yesterday.
17. “How is that possible?” How is that possible? (How could this issue occur?)
16. “It must be a hardware problem.” It must be a hardware problem.
15. “What did you type in wrong to get it to crash?” What did you type in wrong to get it to crash?
14. “There is something funky in your data.” There is something funky in your data.
13. “I haven’t touched that module in weeks!” I haven’t touched that module in weeks!
12. “You must have the wrong version.” You must have the wrong version.
11. “It’s just some unlucky coincidence.” It’s just some unlucky coincidence.
10. “I can’t test everything!” I can’t test everything! (I can’t test every possible scenario in my environment.)
09. “THIS can’t be the source of THAT.” THIS can’t be the source of THAT.
08. “It works, but it hasn’t been tested.” It works, but it hasn’t been tested.
07. “Somebody must have changed my code.” Somebody must have changed my code.
06. “Did you check for a virus on your system?” Did you check for a virus on your system?
05. “Even though it doesn’t work, how does it feel? Even though it doesn’t work, how does the code feel to you?
04. “You can’t use that version on your system.” You can’t use that version on your system. (The program version conflicts with your system.)
03. “Why do you want to do it that way?” Why would you want to do it that way?
02. “Where were you when the program blew up?” Where were you when the program blew up? (What were you doing when it crashed?)
01. “It works on my machine” It works on my machine!!! (Subtext: How come it’s broken on yours?!!!)
Source: Katelynn Eaton