As an old school developer I prefer end-to-end tests and integrated invariant checks. Unfortunately the TDD crowd is currently dominating the debate. The benefits of that methodology are very domain-specific but any kind of nuanced discussion is typically drowned out by one-size-fits-all claims.
At least for C++ there is some light at the end of the tunnel as unit testing rates have started going down; hopefully the saved time has been spent on better design, documentation, and system testing: jetbrains.com/research/devecosyste...
That's an interesting take on the pros and cons of TDD ... the problem with unit tests is often that too much trivial testing is done which is just extra code that needs to be maintained ... if done poorly then it's more of a hindrance than a benefit ... that's why deciding what to test is so important ... think before you act.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very nice introduction. Thank you Aly!
As an old school developer I prefer end-to-end tests and integrated invariant checks. Unfortunately the TDD crowd is currently dominating the debate. The benefits of that methodology are very domain-specific but any kind of nuanced discussion is typically drowned out by one-size-fits-all claims.
At least for C++ there is some light at the end of the tunnel as unit testing rates have started going down; hopefully the saved time has been spent on better design, documentation, and system testing:
jetbrains.com/research/devecosyste...
That's an interesting take on the pros and cons of TDD ... the problem with unit tests is often that too much trivial testing is done which is just extra code that needs to be maintained ... if done poorly then it's more of a hindrance than a benefit ... that's why deciding what to test is so important ... think before you act.