3 ms·
Interesting article but I think the number of projects (100) is very low for valid conclusions. If you have already automated the process maybe you should try
by kkapelon 9y ago
Interesting article but I think the number of projects (100) is very low for valid conclusions.
If you have already automated the process maybe you should try adding more projects.
>Unit Testing Appears to Make Complexity and Method Length Worse
I think it is the other way around. People are forced to write unit tests for complex and big methods. So not as negative as your present it.
- theptip 9y ago> I think it is the other way around. People are forced to write unit tests for complex and big methods. Intuitively this seems correct to me, at least for the code-first paradigm. I do wonder if this holds in the TDD paradigm though, since in that case there are (should be?) tests for everything regardless of complexity. It would be interesting to try to answer this question with further experimentation along the lines of the OP, though I can't think of any way of detecting/classifying projects as TDD vs. not-TDD without contacting the repository authors (which would be time-consuming, potentially prohibitively so).