Session 5.4 - System Testing & Defect Handling
Chapter 9: Integration & System Testing | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- Design system tests from requirements and scenarios
- Run tests with disciplined data capture
- Handle defects efficiently and keep metrics accurate
- Distinguish black-box vs. white-box application at system level
Introduction
System testing validates the full product against requirements. Chapter 9 stresses planning tests early, executing with discipline, and managing defects to avoid thrash.
System Test Design
- Derive cases from SRS and scenarios (normal, boundary, error).
- Use both black-box (external behavior) and white-box (structure where feasible).
- Prioritize critical flows and high-risk areas.
Execution & Data
Best Practices
- Use repeatable data sets and environments.
- Log each run: test id, inputs, expected/actual, pass/fail.
- Capture time spent; keep tests under version control.
Defect Handling
| Step | Description |
|---|---|
| Log | Record defect with clear repro steps, environment, severity. |
| Assign & Fix | Owner fixes; follow coding standards; note time/phase of injection/removal. |
| Retest | Verify fix; regression if needed. |
| Track Metrics | Maintain defect density, removal phase, and fix time data. |
Summary
- System tests come from SRS/scenarios; cover normal, boundary, and error paths.
- Execute with repeatable data and disciplined logging.
- Defect handling must be systematic: log, assign, fix, retest, track.
- Accurate metrics enable process improvement and future estimation.