Developers vs. Quality Control and Assurance

Developers see the world in different colours compared to the QA people

How developers fix bugs (defects) from the QA viewpoint

Software Fix 1 Software Fix 2 Software Fix 2
This should hold us over. It worked yesterday. This is designed according to specification.
Software Fix 4 Software Fix 5 Software fix 6
This is a good fix. It will work this way. Here you go.
Software Fix 7 Software Fix 8 Software fix 9
It will work until the next release. It must be a hardware problem. I did my best.

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”