On 2015-08-29 08:27, Roland Bock wrote:
Instead of assuming code smells or other non-factually based
suppositions, consider examining the coverage of the unit test suite and the rigorous testing regime run each and every commit and taking some hours to complete. I would do that, once I understand, what needs to be tested. And btw, I know you are fully aware, that the quality of tests does not depend on coverage or the amount of time spent on running them. So why bring that up all the time? Another personal opinion, but please search the Internet before calling it unfounded or non-factual: Long running per-commit tests actually are a bad thing since they slow down development considerably.
I suggest trying to re-design your tests in such a way that they run much faster.