| 1: | In the Year 2000 bug example, did Dave do anything wrong? |
| A1: | If Dave was a good programmer he would have questioned the "obvious" oversight and not just programmed his software to only work through 1999. Because he didn't, a software tester should have tested for and found the bug. The team could have then decided whether to fix it. |
| 2: | True or False: It's important what term your company or team calls a problem in its software. |
| A2: | False. It's not important, but the term used often reflects the personality of the team and how they approach the finding, reporting, and fixing of the problems. |
| 3: | What's wrong with just testing that a program works as expected? |
| A3: | At most, that's only half the testing problem. Users don't always follow the rules, and testers need to prove out what happens when they don't. Also, if testers don't approach their testing with a gotta-break-it attitude, they will miss bugs. |
| 4: | How much more does it cost to fix a bug found after the product is released than it does from the very start of the project? |
| A4: | From 10 to 100 times or even higher! |
| 5: | What's the goal of a software tester? |
| A5: | The goal of a software tester is to find bugs, find them as early as possible, and make sure they get fixed. |
| 6: | True or False: A good tester relentlessly strives for perfection. |
| A6: | False. A good tester knows when perfection isn't attainable and when "good enough" is reached. |
| 7: | Give several reasons why the product specification is usually the largest source of bugs in a software product. |
| A7: | Often a spec isn't even writtenremember, if you can't say it, you can't do it. Other reasons are that the spec exists but it isn't thorough, it's constantly changing, or it's not communicated to the rest of the development team. |
