Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 4:
DYNAMIC TESTING (4.1 Test Development Process ( Test Dev…
-
4.2 Type of Test design Techniques
Purpose: identify test condition,
test case and test data
Experience Base Tech
- Experience Base : Knowledge and experience of peple
- No Access to program code
- Require knowledge about issues, bugs, domain of likely defect
- Require knowledge of tester, Dev, user and other stackeholder about the SW, its usage and its environment in one source of infor
- Find defects that miss by spec and struct base
- Apply after formal technical
- Unsystematic
- Usefull in case: Time pressure and poor document
Techniques
- Exploratory Testing
- Error guessing = Fault Attack
Exploratory Testing
- Is concurrent test design, test execution, test log and learning based on a test charter containing test objectives and carried out within time-boxes
- Is an approach that is most useful where there are few or inadequate spec and server time pressure, or in order to augment or complement other more formal testing
- It can serve as a check on the test process. to help ensure that most serious defect are found
Error Guessing or Fault Attack
- Non-systematic test tech
- Deriving TC that attack past failures
- These defect and failure list can be built base on experience, available defect and failure data and from common knowledge about why SW failure
Structural Base Tech
(WHITE BOX TEST)
- Structural Base
- Has access to program code
- Required knowledge of program code
- Apply only to unit test
- Information about how the software is constructed is used to derived the TC ( Ex: code or detail design information)
- The extent of coverage of the SW can be measured for existing TC, and the further TC can be derived systematically to increase coverage
Techniquies
- Statement Coverage
- Decision/Branch Coverage
- Path Coverage
- Linear Code Sequence And Jump (LCSAJ)
Coverage
- Measure % of statement exercise
- Measure % of decision outcome exercise
- Measure % of path exercise
Specification Base Tech
( BLACK BOX TEST)
- Specification Base
- No access to program code
- Required external perspective (Does not use any information regarding internal structure of component or system to be test)
- Apply all phase of testing
- Include both function and non-functional
- Model, either formal or informal are used for the spec of the problem to be solved, the SW or its component
- TC are derived systematically from these models
Techniquies
- Equivalence Partitioning
- Boundary Value Analysis
- Decision Tables
- State Transition Testing/State Table
- Use Case Testing
Coverage
- Cover Valid & Invalid Partition
- Cover minimum and maximum of valid and Invalid partition
- Cover all column of table
- Cover all state, all transitions/ Cover specific transition
- Cover a main stream, alternative flows
-
