PPT and video are due: no later than November 16, 5:00 PM CEN 4072 Software Testing PPT12: Fixing the defect PPT and video are due: no later than November 16, 5:00 PM Submit to: lpiegl@gmail.com This template file is just an outline of the presentation that you need to complete. Additional pages will be necessary to fully explore the topic above. Each page should contain adequate text as well as illustrations. You are free to use all publically available information (text as well as graphics) as long as the sources are properly acknowledged.

Team members’ contributions Member [name]:

From defect to failure Content outline: How a defect becomes a failure? Illustration and explanation

From defect to failure Content outline: How to locate the defect? Explanation and pseudocode

Techniques for locating defects Content outline: Infections, dependences, causes, anomalies, code smells

Techniques for locating defects Content outline: How to integrate all these techniques?

Focusing on errors Content outline: Focus on specific origins: assertions anomalies causes

Focusing on errors Content outline: Focus on infections causes anomalies code smells dependences

Techniques: dependences Content outline: Explanation and graphical illustration

Techniques: observation Content outline: Explanation and graphical illustration

Techniques: assertion Content outline: Explanation and graphical illustration

Techniques: anomaly Content outline: Explanation and graphical illustration

Techniques: cause transition Content outline: Explanation and graphical illustration

Techniques: ordering Content outline: 1- Infections, 2- causes, 3- anomalies, 4- code smells, 5- dependences

Techniques: ordering Content outline: Tracing infections: a complexity challenge

Is the error a cause? Content outline: Example and explanation

Is the cause an error? Content outline: Is making the symptom disappear an acceptable solution? Example code an explanation

Debugging into existence Content outline: Changing the code to make it work without understanding the cause Potential side effects

Devil’s guide to debugging Content outline: Find the defect by guessing Use the most obvious fix

Correcting the defect Content outline: Does the failure no longer occur? Did the correction introduce new problems?

Correcting the defect Content outline: Was the same mistake made elsewhere? Did I commit the change?

Workarounds Content outline: Why workarounds may be necessary? Under what circumstances are they allowed?

Famous workarounds Content outline: Spam filters Virus scanners Date windowing

Learning from mistakes Content outline: Improve quality assurance Improve test suite Setup assertions

Learning from mistakes Content outline: Improve the software process Improve analysis tools

Facts on fixes Content outline: The size of fixes with respect to other changes Fixes and failures

Facts on fixes Content outline: Fixes and older modules Newly written code versus old code