tag:blogger.com,1999:blog-4585201738600758310.post25245999287594426..comments2008-11-23T20:21:35.678ZComments on The Automated Tester: Testing through the Credit Crunch - Part 1 - Devel...David Burnshttp://www.blogger.com/profile/11233457684822187675noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4585201738600758310.post-90271199921669556742008-11-23T14:59:00.000Z2008-11-23T14:59:00.000ZI agree with Liz. In my group, I see a lot of ver...I agree with Liz. In my group, I see a lot of very expensive problems that could have been avoided with better quality at the front end of the process...more emphasis on getting requirements right and unit testing.Marlena Comptonhttp://www.blogger.com/profile/16415917485163679823noreply@blogger.comtag:blogger.com,1999:blog-4585201738600758310.post-89175804097902756222008-11-21T17:05:00.000Z2008-11-21T17:05:00.000ZYes, indeed, Exactly. Though in some organisations...Yes, indeed, Exactly. Though in some organisations this might be the role of the developer. I think a lot of the testing should be happening way before the code gets written, back when the requirements are defined. Even in an agile methodology the story starts when the business wants something (a requirement) and a lot of potential defects can be avoided by having someone with the attributes of a tester being involved in the initial discussions. I'm looking forward to Part 2 of this, so don't take tooo long!Liznoreply@blogger.com