Funny replies developers give to testers..
Top 20 replies by Programmers to Testers when their programs don't work:
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 hasn't 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. "It works on my machine"
posted by Techie @ 4:01 PM
10 comments
QTP and Winrunner Questions and Answers
Contact: qualityvista @ gmail.com
10 Comments:
Hehe, thats funny
I completely agree to all you said. May I mention the different expressions you get in addition.
ya it is absolutly tru..No one agree that it is bug & it is because of his/her coading
Another one-
"That is not a bug; that was a requirement."
[Which obviously the developers gathered verbally from the client and happily forgot to mention to the QA team!]
yaaaaaaa!!!!!!!!!!!!! its really tru,I have experienced all these foolish ans,and another ans is like this "now i dont have time !! report in next testing,now m not goin 2 remove it!!!!"
some times programmers say that "plz clear ur cache, before testing" ....bla bla bla
some times programmers say that "plz clear ur cache, before testing" ....bla bla bla
Agreed....experienced same responses
cooooooool:)
"Of course there will be defects, we planned for half the development time now, and half development during testing"
personal favourite is "that's not a bug, it's a feature".
Post a Comment
<< Home