어쨌건간에 흘러가는 者

본 포스트는 개인 스터디 용으로 작성된 Ian Sommerville의 Software Engineering, 8/E의 요약본입니다.

1. The testing process
- Component testing(unit testing)
  1) Testing of individual program compoents
  2) Usually the responsibility of the component developer
- System testing
  1) Testing of groups of components integrated to create a system or sub-system
  2) The responsibility of an independent testing team
  3) Tests are based on a system specification

2. Testing progress goals
- Validation testing : demonstrate the S/W meets its requirements. A successful test shows that the system operates as intended
- Defect testing : discover faults or defects in the S/W. A successful test exposes defects in the system

3. Testing policies
- Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible
- Testing policies define the approach to be used in selecting system tests. e.g. All functions accessed throught menus should be tested

4. System testing
- Involves integrating components to create a system or sub-system
- Two phases of testing : Integration testing, Release testing

5. Integration testing
- The test team have access to the system source code
- The system is tested when components are integrated
- To simplify error localisation, system should be incrementally integrated

6. Release testing
- The process of testing a release of a system that will be distributed to customers
- Primary goal is to increase the supplier's confidence that the system meets its requirements
- Release testing is usually black-box or functional testing : based on the system specification only

7. using UML
- Use cases can be a basis for deriving the tests for a system. They help identify operations to be tested and help design the required test cases
- From an associated sequence diagram, the I/O to be created for the tests can be identified

8. Performance testing
- test emergent properties of system, such as performance and reliability
- In test plan, the load is steadily increased untiil system performance becomes unacceptable

9. Stress testing
- Exercises the system beyond its maximum design load
- Stressing the system test failur behaviour. Systems should not fail catastrophically

10. Component testing
- Component or unit testing is the process of testing individual components in isolation
- It is a defect testing process

11. Interface testing
- Objectives are to detect faults due to interface errors or invalid assumptions about interfaces
- Particularly impotant for OOD