CIS 2750
True or False: Testing is the same as debugging. - Answer- False. Testing is the systematic
attempt to break a program, while debugging is the process of fixing and removing errors.
True or False: Testing can take upwards of 40 percent of total development time. - Answer- True.
It is not unusual for developers to spend 40% of the total project time on testing.
• For life-critical software (e.g. flight control, reactor monitoring), testing can cost 3 to 5
times as much as all other activities combined.
True or False: Testing can prove the absence of errors. - Answer- False, testing cannot show (or
prove!) the absence of defects -- it can only show that software defects are present.
Testing - Answer- The process of executing a program with the intent of finding an error.
A ____ test case is one that has a high probability of finding an as yet undiscovered error. -
Answer- Good
A __________ test is one that uncovers an as yet undiscovered error. - Answer- Successful
Testing should systematically uncover _________ _______
of errors in a minimum amount of time and with a minimum amount of effort. - Answer- Different
Classes
• A secondary benefit of testing is that it demonstrates that the software appears to be
working as stated in the specification.
• The data collected through testing can also provide an indication of the software's reliability and
quality.
Typographical errors are ______. - Answer- Random
Logic errors and incorrect assumptions are _________ ____________ to the probability that a
program path will be executed. - Answer- Inversely Proportional
• General processing tends to be well understood, while special case processing tends to be
prone to errors.
• However, we often believe that a logical path is not likely to be executed when in
fact, it may be executed on a regular basis.
• Our unconscious assumptions about control flow and data lead to design errors that
can only be detected by testing.
Black Box Testing - Answer- • Consider only public interface of module or entire program
• Apply inputs → examine outputs → compare to spec
• Ideally done by independent testing group - NOT the original programmer
True or False: Testing is the same as debugging. - Answer- False. Testing is the systematic
attempt to break a program, while debugging is the process of fixing and removing errors.
True or False: Testing can take upwards of 40 percent of total development time. - Answer- True.
It is not unusual for developers to spend 40% of the total project time on testing.
• For life-critical software (e.g. flight control, reactor monitoring), testing can cost 3 to 5
times as much as all other activities combined.
True or False: Testing can prove the absence of errors. - Answer- False, testing cannot show (or
prove!) the absence of defects -- it can only show that software defects are present.
Testing - Answer- The process of executing a program with the intent of finding an error.
A ____ test case is one that has a high probability of finding an as yet undiscovered error. -
Answer- Good
A __________ test is one that uncovers an as yet undiscovered error. - Answer- Successful
Testing should systematically uncover _________ _______
of errors in a minimum amount of time and with a minimum amount of effort. - Answer- Different
Classes
• A secondary benefit of testing is that it demonstrates that the software appears to be
working as stated in the specification.
• The data collected through testing can also provide an indication of the software's reliability and
quality.
Typographical errors are ______. - Answer- Random
Logic errors and incorrect assumptions are _________ ____________ to the probability that a
program path will be executed. - Answer- Inversely Proportional
• General processing tends to be well understood, while special case processing tends to be
prone to errors.
• However, we often believe that a logical path is not likely to be executed when in
fact, it may be executed on a regular basis.
• Our unconscious assumptions about control flow and data lead to design errors that
can only be detected by testing.
Black Box Testing - Answer- • Consider only public interface of module or entire program
• Apply inputs → examine outputs → compare to spec
• Ideally done by independent testing group - NOT the original programmer
