Static testing - Session 3 have content overview: reviews and the test process, types of review, static analysis, static techniques do not execute code. | Static Testing Session 3 Overview Reviews and the test process Types of review Static analysis People techniques individual: desk-checking, data-stepping, proof-reading group: Reviews (informal & formal): for consensus Walkthrough: for education Inspection (most formal): to find faults Static techniques do not execute code Benefits of reviews Development productivity improvement Reduced development timescales Reduced testing time and cost Lifetime cost reductions Reduced fault levels Improved customer relations etc. Reviews are cost-effective 10 times reduction in faults reaching test, testing cost reduced by 50% to 80% Freedman & Weinberg, Handbook of Walkthroughs, Inspections & Technical Reviews reduce faults by a factor of 10 Yourdon, Structured Walkthroughs 25% reduction in schedules, remove 80% - 95% of faults at each stage, 28 times reduction in maintenance cost, many others Gilb & Graham, Software Inspection What can be Inspected? policy, strategy, business plans, marketing or advertising material, contracts system requirements, feasibility studies, acceptance test plans test plans, test designs, test cases, test results system designs, logical & physical software code user manuals, procedures, training material Anything written down can be Inspected What can be reviewed? anything which could be Inspected . anything written down plans, visions, “big picture”, strategic directions, ideas project progress work completed to schedule, etc. “Should we develop this” marketing options What to review / Inspect? Tests Tests Tests Tests Requirements Design Code Functions Integration Test Unit Test Accept. Test System Test Costs of reviews Rough guide: 5%-15% of development effort half day a week is 10% Effort required for reviews planning (by leader / moderator) preparation / self-study checking meeting fixing / editing / follow-up recording & analysis of statistics / metrics process improvement (should!) Overview Reviews and the | Static Testing Session 3 Overview Reviews and the test process Types of review Static analysis People techniques individual: desk-checking, data-stepping, proof-reading group: Reviews (informal & formal): for consensus Walkthrough: for education Inspection (most formal): to find faults Static techniques do not execute code Benefits of reviews Development productivity improvement Reduced development timescales Reduced testing time and cost Lifetime cost reductions Reduced fault levels Improved customer relations etc. Reviews are cost-effective 10 times reduction in faults reaching test, testing cost reduced by 50% to 80% Freedman & Weinberg, Handbook of Walkthroughs, Inspections & Technical Reviews reduce faults by a factor of 10 Yourdon, Structured Walkthroughs 25% reduction in schedules, remove 80% - 95% of faults at each stage, 28 times reduction in maintenance cost, many others Gilb & Graham, Software Inspection What can be Inspected? policy, strategy, business .
