tag:blogger.com,1999:blog-6959582839690958035.post2595301467494242995..comments2023-09-15T11:15:54.222-04:00Comments on public void Life(): Test Everything. Every Time.testhttp://www.blogger.com/profile/09609860522747123959noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6959582839690958035.post-49889623854582285482011-09-15T09:00:49.562-04:002011-09-15T09:00:49.562-04:00I'll readily admit that I have not developed t...I'll readily admit that I have not developed those skills. But as a consultant it's just as important that I find a resource to add to the team who has. After all, writing the tests can happen outside of writing the code, so it's a task that can be offloaded to a separate resource. (Often at less cost to the client, since for us that resource will likely be at a discounted rate from our dev farm, which isn't as sinister as it sounds.)<br /><br />I need to read more from Uncle Bob. I'll probably finally buy Clean Code today, or whatever it's called. He's definitely right, and I quote him often on the subject. The client may complain that writing automated tests costs so much more than just doing it manually. But how much more? 10x? 20x? Even if it's that high, can they honestly say that they're only ever going to need to test their software 20 times in its entire life? There will only be 20 releases to production, no more? Doubtful.testhttps://www.blogger.com/profile/09609860522747123959noreply@blogger.comtag:blogger.com,1999:blog-6959582839690958035.post-38513891811130323672011-09-15T08:45:54.759-04:002011-09-15T08:45:54.759-04:00Yeah I agree. I feel like with out proper automate...Yeah I agree. I feel like with out proper automated testing there is no way you can have long term continuous productivity. I think that without a solid continuous integration and continuous testing (automated testing for the most of it) in place you'll be slowly going down hill and chasing your tail. Worse you may not realize it if you are not properly tracking metrics, which is very hard.<br /><br />Of course writing and maintain tests is a skill and a discipline that has to be developed as well. I'm hoping to further mine, but in my experience very few people have spent anytime on it. All to easy for someone to jump straight into code, click through some things, and pass it along. Or worse someone looks down on the practice because it takes extra coding time to write and maintain. <br /><br />Listen to Uncle Bob, you don't have the time to not test.Copenhashttps://www.blogger.com/profile/14860283098628466896noreply@blogger.com