Seven Principles of SW Testing

Can you prove there are no defects in a SW product?

• Sometimes - If we have enough time

• Yes - Using formal methods

• Sometimes - for well written code

• No - it's always impossible

How many tests are needed to test code that implements this flow?

• 1800

• 180

• 1,000,000,000,000,000,000

• 112500

When is the best time in a SW project to start testing?

• When the product is being defined

• The minute the first line of code is written

• When the coding is completed

• Once the first feature is completed

I tested 3 modules of a system. Where should I focus the testing of the next version?

• On Module A

• On Module B

• On all modules at the same level

• On Module C

The designed tests were run, all bugs were fixed and all tests are passing. Am I done testing?

• Yes - because you found all the bugs

• No - because you didn't find all the bugs

• No - exhaustive requirement coverage is not possible

• Yes - if you covered all the requirements

I dropped a hand calculator. What influences the type of tests I will run to check it?

• The defined specifications for this calculator

• Where this calculator is going to be used

• What it will be used for

• The risk involved in the calculator not working

I did it! I developed a program with 0 bugs. Does it guarantee the program will sell well?

• Yes - see how well Windows sells

• Yes - people are tired of programs that fail

• No - a Zero-bug program is not possible

• No - it may be doing something not useful