Black-box Testing Doesn 't require explicit knowledge of the internal structure of the system Primarily focuses on functional requirements User-perspective Validates the spec Input Output
11 Black-box Testing • Doesn’t require explicit knowledge of the internal structure of the system • Primarily focuses on functional requirements – User-perspective – Validates the spec Input Output
te-box testing Requires knowledge of the internal structure Primarily focuses on code coverage e.g. write tests to“ cover”' internal paths Good for testing individual functions Developers tests Input Output
12 White-box testing • Requires knowledge of the internal structure • Primarily focuses on code coverage – e.g. write tests to “cover” internal paths – Good for testing individual functions – Developer’s tests Input Output
Risk-based Testing Used to determine What to test T est priori Test coverage
13 Risk-based Testing • Used to determine: – What to test – Test priority – Test coverage
Risk-based Testing High High LoW High Medium Medlium Medium OW Low LOW High Impact
14 Risk-based Testing
Risk-based Testing Two basic factors for determining risk Impact to the customer Probability of customer experiencing issues Other factors affecting risk assessment History, complexity, usability, dependencies,new features or technologies, modifications, etc Value of risk assessment Prioritize work Scope testing effort 15
15 Risk-based Testing • Two basic factors for determining risk: – Impact to the customer – Probability of customer experiencing issues • Other factors affecting risk assessment: – History, complexity, usability, dependencies, new features or technologies, modifications, etc. • Value of Risk Assessment – Prioritize work – Scope testing effort