어쨌건간에 흘러가는 者 ::

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

1. Test case design
- The goal of test case design is to create a set of tests that are effective in validation and defect testing
- Use experience and guidelines to design test cases in defect testing
- Design approaches
1) Requirements-based testing
2) Partition testing
3) Structural testing
4) Path testing

2. Requirements based testing
- A general principle of requirments engineering is that requirements should be tesable
- is a validation testing technique where you consider each requirement
- derive a set of tests for that requirement

3. Partition testing
- Equivalence partitioning is a way of discovering test cases - all cases in a partition should behave in the same way
- Input data and output results often fall into different classes where all members of a class are related
- Each of these classes in an equivalence partition or domain where the program behaves in an equivalent way for each class member
- Test cases should be chosen from each partition

4. Structural testing
- Sometime called white-box testing
- Derivation of test cases according to program structure. Knowledge of the program is used to identify addtional test cases
- Objective is to exercise all program statements(not all path combinations)

5. Path testing
- The objective of path testing is to ensure that the set of test cases is such that each path through the program is executed at least once
- The starting point ofr path testing is a program flow graph that shows nodes representing program decisions and arcs representing the flow of control
- A dynamic program analyser may be used to check that paths have been executed

6. Test automation
- Testing is an expensive process phase
- Test automation tools are called as testing workbench
- Most testing workbenches are open systems because testing needs are organisation-specific
- Scripts may be developed for UI simulators and patterns for test data generators