The death of Cannot Reproduce
Software practitioners believe if you cant reproduce a bug, you cant know if youve fixed it, but sometimes it's just not possible. Issue tracking systems have a special resolution type for this situationCannot Reproduce. Michelle Brush highlights principles and practices that deliver reproducibility in systems, arguing that we are getting closer and closer to the death of Cannot Reproduce.
| Talk Title | The death of Cannot Reproduce |
| Speakers | Michelle Brush (Cerner Corporation) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | London, United Kingdom |
| Date | October 16-18, 2017 |
| URL | Talk Page |
| Slides | |
| Video | Talk Video |
Software practitioners believe if you can’t reproduce a bug, you can’t know if you’ve fixed it. This belief has led to many long days and late nights spent trying to brute force a system into behaving just as the bug report described to no avail. Issue tracking systems have a special resolution type for just this situation—Cannot Reproduce. What does it mean when we can’t reproduce an issue? It means there are variables outside our understanding of the system, such as inconsistent configuration in the environment, state that isn’t observable, or race conditions happening in real time. However, things are getting better. Michelle Brush highlights modern programming principles and practices that deliver reproducibility in systems, arguing that these approaches are bringing us closer and closer to the death of Cannot Reproduce.
