http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I have read that, but I don't agree with you on this. It is not that GUI is hard to test, (and it is, even with TypeMock, because you have complex user interactions), it is the permise that you shouldn't design for SRP & SoC that bother me. http://ayende.com/2538/tools-vs-design#comment4http://ayende.com/2538/tools-vs-design#comment4Mon, 11 Jun 2007 14:37:45 GMTI've worked with plenty of people that argue that separation of concerns and single responsibility increase complexity and make code too "abstract," so they probably enjoyed the article :P http://ayende.com/2538/tools-vs-design#comment3http://ayende.com/2538/tools-vs-design#comment3Mon, 11 Jun 2007 14:01:44 GMTOren, you should read the end of the sentence that you are quoting "and overcome the forbidden decree that GUI is hard to test" This is the reason to avoid separating concerns. Our differences are not Tools vs Design but Design vs. Process http://www.elilopian.com/2007/06/11/design-vs-process/ http://ayende.com/2538/tools-vs-design#comment2http://ayende.com/2538/tools-vs-design#comment2Mon, 11 Jun 2007 13:28:37 GMTThe only possible explanation would be legacy code you can't change. But then, perhaps a quick refactor of the code, followed by your unit tests is in order. The more time you put into a unit test to make it work around limitations in your design, the more likely you are to introduce new and wonderful bugs, probably in your unit tests. I think this falls into the same bracket as unit testing private methods... it implies something is rotten in the state of Denmark! http://ayende.com/2538/tools-vs-design#comment1http://ayende.com/2538/tools-vs-design#comment1Mon, 11 Jun 2007 07:19:11 GMT