tag:blogger.com,1999:blog-8648268364549955959.post7991114042096586329..comments2024-03-29T04:52:24.663+00:00Comments on the literate programmer: Communicative testingctfordhttp://www.blogger.com/profile/05464902188219000642noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8648268364549955959.post-67428330799031179852021-11-22T03:50:09.331+00:002021-11-22T03:50:09.331+00:00Appreciate youu blogging thisAppreciate youu blogging thisEvan Staffordhttps://www.evanstafford.com/noreply@blogger.comtag:blogger.com,1999:blog-8648268364549955959.post-33109548286664090262010-11-07T21:08:37.020+00:002010-11-07T21:08:37.020+00:00It's a similar dilemma to convincing managers ...It's a similar dilemma to convincing managers that code quality is important (or that it even exists).<br /><br />I suppose the answer is that teams have to earn enough trust that they are empowered to choose the practices that will make them most productive.<br /><br />If people outside the team are make inappropriately detailed decisions, they'll probably get them wrong.<br /><br />Sometimes extra investment in testing makes sense, and sometimes it doesn't. The people best placed to make that call are the developers themselves.ctfordhttps://www.blogger.com/profile/05464902188219000642noreply@blogger.comtag:blogger.com,1999:blog-8648268364549955959.post-53887401049679296872010-11-05T22:40:19.543+00:002010-11-05T22:40:19.543+00:00The main problem is time to turn normative tests i...The main problem is time to turn normative tests into informative tests.<br /><br />I can tell you from the stack trace that the script failed because it has tried to interact with a hidden element, so it is reasonably informative. <br /><br />Will management provide us with the time and resource to take this information and make it even more informative so that you don't need a tester who understands the nuts and bolts of the system to interpret it? Or will the testers be given a whole load of new work to test with an assumption made that code shouldn't really break so we don't need to worry about informative reporting until it does break (lets hope the guy who wrote that script is still working for us when it does break....)?<br /><br />The question is how do we convince those higher up the chain that the extra time and investment to make the tests informative is worthwhile?Ardescohttps://www.blogger.com/profile/10553907442689592790noreply@blogger.com