This Q&A is part of a weekly series of posts highlighting common questions encountered by technophiles and answered by users at Stack Exchange , a free, community-powered network of 100+ Q&A sites . is4 asks: I usually try to follow the advice of the book Working Effectively with Legacy Code . I break dependencies, move parts of the code to @VisibleForTesting public static methods and to new classes to make the code (or at least some part of it) testable. And I write tests to make sure that I don’t break anything when I’m modifying or adding new functions. A colleague says that I shouldn’t do this. His reasoning: The original code might not work properly in the first place. And writing tests for it makes future fixes and modifications harder since devs have to understand and modify the tests too. If it’s GUI code with some logic (~12 lines, 2-3 if/else blocks, for example), a test isn’t worth the trouble since the code is too trivial to begin with. Similar bad patterns could exist in other parts of the codebase, too (which I haven’t seen yet, I’m rather new); it will be easier to clean them all up in… Read full this story
- Victorian schools to use rapid testing to cut quarantine time as state records 1,126 new cases
- Why Developers Need More Insights Into Low-Code Tools
- Green list travel: The simple mistake you might making with your PCR tests - 'No upside'
- iOS 15.2 Public Beta 2 Brings Legacy Contacts, Private Email Addresses, And More
- How Do You Write an Anthony Bourdain Book Without Anthony Bourdain?
- How Selena's glorious legacy shows off the vast complexity of Latinos
- Betrivers Sportsbook Promo Codes and Review
- How to perform rapid antigen test at home. 7 tips to get accurate result
- 'Eternals' adds another blockbuster to Jack Kirby's Marvel-ous legacy
- Personality Tests Are the Astrology of the Office
Should I write tests for legacy code if there’s no time for refactoring? have 311 words, post on arstechnica.com at June 7, 2014. This is cached page on Vietnam Colors. If you want remove this page, please contact us.