3 ms·
I disagree with >Create Utility Classes and Functions/Methods This doesn't make something untestable. Take for example a max function. A max function such as
by charcircuit 5y ago
I disagree with
>Create Utility Classes and Functions/Methods
This doesn't make something untestable. Take for example a max function. A max function such as Math.max is a part of a utility class, but it's easy to test.
- mertd 5y agoI believe they mean utility classes which would need explicit instantiation and lifetime management to run any test that might call them at some point like: MathOperationsProvider::Init(endianness_config, locale, wolfram_alpha_connection).
- drewcoo 5y agoIf you can't justify it. And keep justifying it every time someone asks. Then don't do it. Max . . . max is pretty easy to justify. But MaxMinusMagicFiveForUnseenReasons . . . not so much. The point of all of this (I assume TotT) is to have the conversations. If you're not having them at design time or code review time or incident response postmortem times, you're doing it wrong. And you're reminded every time you visit the restroom (again, if it's TotT). That's my interpretation.
- charcircuit 5y agoThat is more of a maintainability problem than a testability problem.