SOFTWARE TESTING

Reaching the end of a job interview, the human resources person asked a QA engineer fresh out of the community college , "And what starting salary were you looking for?" The engineer said, "In the neighborhood of $125,000 a year, depending on the benefits package." The interviewer said, "Well, what would you say to a package of 5-weeks vacation, 14 paid holidays, full medical and dental, company matching retirement fund to 50% of salary, and a company car leased every 2 years - say, a red Corvette?" The Engineer sat up straight and said, "Wow! Are you kidding?" And the interviewer replied, "Yeah, but you started it."

Top 24 replies by programmers when their programs don't work: 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...

Software doesn't just appear on the shelves by magic. That program shink-wrapped inside the box along with the indecipherable manual and 12-paragraph disclaimer notice actually came to you by way of an elaborate path, through the most rigid quality control on the planet. Here, shared for the first time with the general public, are the inside details of the program development cycle. 1. Programmer produces code he believes is bug-free. 2. Product is tested. 20 bugs are found. 3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs. 4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs. 5. See 3. 6. See 4. 7. See 5. 8. See 6. 9. See 7. 10. See 8. 11. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released. 12. Users find 137 new bugs. 13. Original programmer, having cashed his royalty check, is nowh...