3.1-Static testing basics
3.1.1 - Work Products that can be examined by Static Testing
3.1.2 - Benefits of Static Testing
-
When applied early in the software development lifecycle, enables the early detection of defects before dynamic testing is performed, examples:
- in requirements
- design specifications reviews
- backlog refinement, etc.
-
Defects found early are often much cheaper to remove than defects found later in the lifecycle, especially when the software is deployed and in active use.
Additional benefits of static testing may include:
- Detecting and correcting defects more efficiently, and prior to dynamic test execution
- Identifying defects which are not easily found by dynamic testing
- Preventing defects in design or coding by uncovering inconsistencies, ambiguities, contradictions, omissions, inaccuracies, and redundancies in requirements
- Increasing development productivity (e.g., due to improved design, more maintainable code)
- Reducing development cost and time
- Reducing testing cost and time
- Reducing total cost of quality over the software’s lifetime, due to fewer failures later in the lifecycle or after delivery into operation
- Improving communication between team members in the course of participating in reviews
3.1.3 - Differences between Static and Dynamic Testing
Last update:
2022-08-21