tag:blogger.com,1999:blog-381129527146258002.post6546941835635646314..comments2024-03-28T04:51:40.042-07:00Comments on Agile Otter Blog: Tests Are CodeAgileotterhttp://www.blogger.com/profile/10773578598860454277noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-381129527146258002.post-54650438004499721562010-10-02T03:05:47.239-07:002010-10-02T03:05:47.239-07:00In my experience the extra code that is needed, of...In my experience the extra code that is needed, often arises from implicit coupling of the UI with the business layer.<br />Another issue that causes this is violating the law of Demeter (using too many gets instead of telling objects what to do).<br />So I would say that this very issue is a bad smell in the original code, and would double check it too see if it needs any refactoring.Darioushnoreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-77486239401923077552010-10-02T03:03:29.689-07:002010-10-02T03:03:29.689-07:00In my experience the extra code that is needed, of...In my experience the extra code that is needed, often arises from implicit coupling of the UI with the business layer.<br />Another issue that causes this is violating the law of Demeter (using too many gets instead of telling objects what to do).<br />So I would say that this very issue is a bad smell in the original code, and would double check it too see if it needs any refactoring.Darioushnoreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-14851145230844951312010-10-01T14:37:49.409-07:002010-10-01T14:37:49.409-07:00For years I was afraid someone will use the "...For years I was afraid someone will use the "test-code" for production and ruin everything. Once I stopped adding those functions with hacks, but treated them as Real Code (TM), I stopped worrying. These extended the design as I needed, and sometimes I later found good uses for them in productionAviv Ben-Yosefhttps://www.blogger.com/profile/08503299667171126821noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-70992751803848560082010-10-01T10:49:34.559-07:002010-10-01T10:49:34.559-07:00On our team we've been gradually moving toward...On our team we've been gradually moving towards a model where test code and production code are considered equal.<br /><br />We have had a past habit of treating the acceptance tests as second class. In our retrospectives we've gradually moved our thinking towards all code has equal status based on trying to solve problems we've had.<br /><br />I sometimes drop the phrase "Automated testing is customer visible," and people tend to agree.<br /><br />I have a hard time imagining this team:<br /><br />1. Adopts a policy of "no test support" in production code.<br />2. Periodically meets to discuss process problems and adopts solutions.<br />3. Manages to stick with that policy.<br /><br />I just can't see how. But I've been wrong before.Darrin Thompsonhttps://www.blogger.com/profile/04037462028265507114noreply@blogger.com