1. Unit Test
- by developer
- 시간, 기술적 이슈사항 발생
- cost effective측면에서 testing a few unit together을 고려할 수도 있음
- Manual review, static analyzer tool사용 가능(but can't completely replace)
- Reviewer의 capacity, 집중력 중요
2. Integration Test
- by developer
- function coverage측정가능
- useless code제거 가능
3. System Test
- not to find bugs but to validate incomplete specification
- Finite test case(so, test case selection is important)
- User req. 충족문제는 별도의 issue가 될 수 있음
- Test environment is simple and easy(개발자 선호)
- only visible bug detect
- low level defect is difficult to detect
- debuggin is difficult
- navigating is difficult because coverage measure is issue.
'잡담' 카테고리의 다른 글
| Computer Network (0) | 2008.03.08 |
|---|---|
| MIS(Management Information System) (0) | 2008.03.08 |
| 생각 (0) | 2008.02.18 |
| Virtual device drivers (0) | 2008.02.15 |
| 생각 (0) | 2008.02.15 |