24. "It works fine on MY computer"
23. "Who did you login as ?"
22. "It's a feature"
21. "It's WAD (Working As Designed)"
20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it's not been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"
1. "I thought I fixed that."
Quoted from: http://www.geocities.com/xtremetesting
5 comments:
25. That's why we need you to test everything, and you are really doing a great job.
26. No WAY !!!!
27. Sue Me
Good add from a programmer ;)
Do we do that?
Some of those replies I recall using, but some are too stupid.
For instance if I was in your shoes and a developer told me you had a virus I would take off the keyboard from its place and...
ow 7'aleeha mastoorah:p
You can say after 2 years of working as a QA, i hav heard almost all of them ;)
I can control myself, instead of using keyboard, i use bug tracker & email :)
P.S. "we" exclude u, cos i hvnt heard u saying any of them ...
I'm flattered :$
Well developers have to understand that you're doing your job so whatever comments you hear just add another bug in the bug tracker:)
Post a Comment