In experience-based techniques, people’s knowledge, skills and background are a prime contributors to the test conditions and test cases.
The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process.
Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing.
In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps:
- Review meeting
- Extreme Programming (XP)
- Lean Software Development
- Feature-Driven Development
- Agile Unified Process
- Dynamic Systems Development Model (DSDM)
- Component Testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are separately testable.
- Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.
- Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components in a simple manner. A stub is called from the software component to be tested; a driver calls a component to be tested.