Component (Unit) Testing Explained | ISTQB CTFL v4.0
These lists of test bases and test objects are not exhaustive but provide examples of each, for component testing:
- Objectives – to discover defects and failures in each unit of code, in isolation, before integration
- Typical defects and failures – if you recall that a defect is something that is written incorrectly, and a failure is observed when behaviour is unexpected, then a defect here would be something written incorrectly in the code, such as 1-20, when 1-10 was intended. The resultant failure could be that a drop-down box shows 20 items when it should show just 10.
- Specific approaches and responsibilities – since testing here is focused on individual pieces of code, it is most often carried out by the developers in their environments, where they have access to test harnesses and unit test frameworks. These are libraries and tools that enable developers to test their units of code before integration.