Object Oriented Software Engineering View all facts Glossary Help |
subject > person or group > person > stakeholder > software developer > tester |
tester comparison table |
Subject | observe | is a subtopic of | design | examine | provide | ensure that | recruit from | give | see | benefit by | know that | perform | report | has definition |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
beta tester | 10.9 - Strategies for Testing Large Systems | tests that explicitly try to catch a range of specific types of defects that commonly occur | the set of use cases is complete and that they are expressed consistently and unambiguously | the potential user population of a product | a pre-release version of the software | using the features of the software before others have access to them | the software will contain more defects than the final version | cost estimation | problems when he or she discovers them | A person performing beta testing | ||||
black-box tester | outputs from the system | 10.2 - Effective and Efficient Testing | tests that explicitly try to catch a range of specific types of defects that commonly occur | inputs to the system | the set of use cases is complete and that they are expressed consistently and unambiguously | the source code, the internal data, nor any of the design documentation describing the system's internals | software developers tend to have certain habits that can lead to errors, and hence to defects | black-box testing | A person performing black-box testing | |||||
glass-box tester | the steps taken by algorithms and their internal data (at run time) | 10.2 - Effective and Efficient Testing | design tests that will exercise all aspects of each algorithm and data structure | the design documents and the code | testing strategy has reached a targeted coverage of statements and branches | software developers tend to have certain habits that can lead to errors, and hence to defects | glass-box testing | |||||||
independent testing group | 10.9 - Strategies for Testing Large Systems | tests that explicitly try to catch a range of specific types of defects that commonly occur | the set of use cases is complete and that they are expressed consistently and unambiguously | software developers tend to have certain habits that can lead to errors, and hence to defects | cost estimation | A testing group separate from those who designed and programmed the system | ||||||||
paraphraser | 10.10 - Inspections | tests that explicitly try to catch a range of specific types of defects that commonly occur | the set of use cases is complete and that they are expressed consistently and unambiguously | software developers tend to have certain habits that can lead to errors, and hence to defects | cost estimation | A person in an inspection who steps through the document explaining it in their own words |
Next software developer: architect Up: software developer Previous software developer: technology specialist