One of the interesting parts of #refactoring code is how you can refactor code and then another possible refactoring shows up, revealing another, and so on. I was able to delete 2 tests because I realized they were identical to another test once I refactored them all three times.
Rector - The Power of Automated Refactoring by Matthias Noback and Tomas Votruba is on sale on Leanpub! Its suggested price is $49.00; get it for $44.10 with this coupon: https://leanpub.com/sh/Ui7OQaXS#Refactoring#Php
Rector - The Power of Automated Refactoring by Matthias Noback and Tomas Votruba is on sale on Leanpub! Its suggested price is $49.00; get it for $44.10 with this coupon: https://leanpub.com/sh/B9IdS8n4#Refactoring#Php
Rector - The Power of Automated Refactoring by Matthias Noback and Tomas Votruba is on sale on Leanpub! Its suggested price is $49.00; get it for $44.10 with this coupon: https://leanpub.com/sh/sM4JRcQc#Refactoring#Php
Heared something today that triggered a pet peeve ("Words don't mean what they don't mean", h/t @davenicolette ), and in my someone-is-wrong-on-the-internet-moment that I'm having right now, I've got to say:
#refactoring is changing the structure of a program WITHOUT changing it's behavior. If you are not feature-to-feature AND bug-to-bug compatible -> not refactoring.
Term I heard: "Refactoring to feature parity" - not wrong, but could be from the department-of-redundancy-department #kthxbye
@mctwist My vice is #refactoring other team members’ code when reviewing their merge requests, especially when they’re making a small fix to some grotty #LegacyCode. (Spoiler: it’s all grotty legacy code)
#homeassistant is rejecting pull-requests that touch config options on projects that still use the old configuration.yaml-way, insisting on a #refactoring first.
Ii will be interesting to see how this is going to play out for them long-term. That's probably the only way to muster the required effort for refactoring the codebase, but I wonder how many necessary updates won't get done.
I'm trying to recall if we ever had something similar in the #FreeBSD ports-tree...don't think so. 1/n
I keep hearing/seeing things like this when justifying not writing a lot of automated tests: "tests often end up needing to be rewritten because the implementation changed."
And that's just not my experience at all. Though it does depend on how the word "rewritten" is interpreted. Do I have to restructure tests? Sure, if, for example, I wrap a long inside of a PlayerId class, then I'm going to have to change any test that uses/expects a long [to now use a PlayerId].
However, refactoring techniques (at least in Java with IntelliJ IDEA) can make this straightforward, often with no manual code changes.
Does anyone have concrete examples of where tests had to be rewritten because of implementation changes?
Did you know that in Extreme Programming (XP), refactoring is not just cleaning up code, but a core practice to boost agility? It's about evolving design organically, embracing change for the ultimate efficiency! #ExtremeProgramming#Refactoring#DevLife 👨💻🔄
Rector - The Power of Automated Refactoring by Matthias Noback and Tomas Votruba is on sale on Leanpub! Its suggested price is $49.00; get it for $44.10 with this coupon: https://leanpub.com/sh/Kgy4Rztl#Refactoring#Php
Rector - The Power of Automated Refactoring by Matthias Noback and Tomas Votruba is on sale on Leanpub! Its suggested price is $49.00; get it for $44.10 with this coupon: https://leanpub.com/sh/kx0Jkk2E#Refactoring#Php