Software Engineering
Home Planning Requirements Writing Hazard Analysis Requirement Analysis Config Control Software Design Software Testing Software Standards Basic Logic

Basic Logic - Examples of Type I and Type II Errors

Recall that with a Type I error, the test passes even though the software contains a defect. With a Type II error, the test execution contains the defect, which means that no conclusion can be drawn about the software (it may or may not contain a defect).

For each statement, decide if this produces a Type I or Type II error.


Stress conditions not fully tested.

   


Defects are timing related (relationship has a chance element).

   


Test objectives incorrectly describe the expected results.

   


Engineers had a different interpretation of the requirements than the testers.

   


Tester uses the program itself as a guide to writing the test (descriptive testing).

   


A second program, which contains a defect, was used to either test or code the system. For example, a spreadsheet that gives incorrect results or a calibration program that makes incorrect settings.

   


Data used is not adequate to create the desired test condition (condition A was not actually being set as intended).

   


The wrong condition was measured (result B was not being read correctly).