I don’t think I’ve met a codebase that had tests that would work with the level of refactoring that would need to be done. I mean let’s be honest here, if it was well architected, refactoring wouldn’t be like the comic. It’s probably a mess of entangled concerns and bad inheritance.
For that matter the code most in need of refactoring probably has shit tests and that just assertNotNull on the happy path to appease sonar and be done with it.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@beehaw.org
All things programming and coding related. Subcommunity of Technology.
Refactoring, without test coverage, in a nutshell.
Definitely adding this one to the dev guidelines on unit and integration tests. 👍🏼
I don’t think I’ve met a codebase that had tests that would work with the level of refactoring that would need to be done. I mean let’s be honest here, if it was well architected, refactoring wouldn’t be like the comic. It’s probably a mess of entangled concerns and bad inheritance.
For that matter the code most in need of refactoring probably has shit tests and that just
assertNotNullon the happy path to appease sonar and be done with it.