Glossary
Following is a list of terms that can be helpful to know when you are dealing with hardware and software testing.
acceptance testing
A software or hardware development test phase designed to demonstrate that the system under test meets requirements. This phase is unique in all test activities in that its sole purpose is to build confidence in the quality of the software. Acceptance testing should not find bugs. Acceptance testing is usually the last test phase before a product is released.
ad hoc testing
Testing without written test cases, documented expected results, a checklist, a script, or instructions. Ad hoc tests often are not captured, which leads to questions about coverage and makes it impossible to do proper regression testing. Ad hoc testing can, however, be useful as a way to develop tests if records are kept. Also called ad-lib testing. Contrast with exploratory testing or software attacks.
behavioral tests
Tests based on what a computer system, hardware or software, is supposed to do. Such tests are usage-based and frequently functional, at the levels of features, operational profiles, and customer scenarios. Also called black-box tests or functional tests.
black-box tests
See behavioral tests.
bug
A problem present in the system under test that causes it to fail to meet reasonable expectations; also called a defect. The symptom of a bug is a failure. The reasonableness of an expectation can be determined by iterative consensus or management fiat if it ...
