A test design technique basically helps us to select a good set of tests from the total number of all possible tests for a given system. There are many different types of software testing technique, each with its own strengths and weaknesses. Each individual technique is good at finding particular types of defect and relatively poor at finding other types.
For example, a technique that explores the upper and lower limits of a single input range is more likely to find boundary value defects than defects associated with combinations of inputs. Similarly, testing performed at different stages in the software development life cycle will find different types of defects; component testing is more likely to find coding logic defects than system design defects.
Each testing technique falls into one of a number of different categories. Broadly speaking there are two main categories:
- Specification-based (black-box testing, also known as behavioral techniques)
- Structure-based (white-box testing or structural techniques)
- Experience- based
Dynamic techniques are subdivided into three more categories: specification-based (black-box, also known as behavioral techniques), structure-based (white-box or structural techniques) and experience- based. Specification-based techniques include both functional and nonfunctional techniques (i.e. quality characteristics).
Other popular articles:
- What is white-box or Structure-based or structural testing techniques?
- What is black-box, Specification-based, also known as behavioral testing techniques?
- What is Experience- based testing technique?
- What is Structural testing (Testing of software structure/architecture)?
- How to choose that which testing technique is best?
nag.swarup says
System testing is a more limited type of testing; it seeks to detect defects both within the “inter-assemblages” and also within the system as a whole.