Object Oriented Software Engineering   View all facts   Glossary   Help

subject > process > verification > testing

testing
subject			fact

testing	can find defects whose consequences are obvious but which are buried in complex code, and thus will be hard to detect when inspecting
	has definition An approach to verification that involves systematically executing software to detect defects
	involves thinking of what could go wrong without actually studying the software
	is complementary to inspecting
	is a subtopic of 10.2 - Effective and Efficient Testing
	is a kind of verification
	requires attention to detail
process	see also process^2

Kinds of testing :

• black-box testing (5 facts) - A form of testing in which you manipulate inputs and observe outputs, but cannot observe the internals of the entity being tested
• boundary testing (3 facts) - A testing strategy based on testing at the boundaries of equivalence classes - since this is where most errors occur
• effective testing (3 facts)
• efficient testing (3 facts)
• equivalence class testing (3 facts) - A testing strategy based on determining the possible equivalence classes and creating a test case for each
• final testing (3 facts)
• glass-box testing (10 facts) (structural testing, white-box testing) - A form of testing in which the tester can examine the design documents and the code, as well as analyze and possibly manipulate the internal state of the entity being tested
• object-oriented testing (3 facts) - Testing that focuses on the specific properties of object oriented programs
• stress testing (3 facts) - Testing on minimal configurations and at peak loads or with missing resources
• testing performed by software engineers (6 kinds, 2 facts)
• testing performed by users and clients (3 kinds, 3 facts)