Uploaded byPeter Antman
Stop the line @spotify
The document discusses the importance of fixing bugs and writing tests in a software development context, likening undetected defects to broken windows. It emphasizes a proactive approach to handling failed tests and defects, and the necessity of maintaining a continuous testing environment. The text is presented in a lyrical format, referencing a 'stop-the-line' philosophy to emphasize attention to quality.
More Related Content
![Governance, Deployment & Methodologies for Agentic Automation [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day2-251112135038-a386476d-thumbnail.jpg?width=640&height=640&fit=bounds)
Stop the line @spotify
- 1. Stop breaking thosewindows P2, P3, P4, P5 Every time you do not fix a bug You breake a new window
- 2. Wetest to makeourproductdefectfree Why dowe write tests?
- 3. What dowedowhena testfails?
- 4. When a testbreakes wefixthe defect
- 6. What dowedowhena bugis discovered?
- 7. Write a test Fixthe bug
- 8. Is that whatyou do? Honestly?
- 9. You should! A bugisjust an unwrittentest that would have failed Andhow didwe handle failed test now again?
- 10. Clean up GoGreen (adaptto capacity) FixNextSprint (Stop-the-line)
- 11. Any defect isa broken window
- 12. The stop-the-line song Ikeep a close watch on these tests of mine I keep my Jenkins open all the time I see a defect coming down the line Becuse you're mine, I stop the line