tag:blogger.com,1999:blog-3055499922775600843.post4165441853194679513..comments2024-03-23T12:28:05.901+00:00Comments on Expected Results: Testing TurtlesPhilhttp://www.blogger.com/profile/00281118161548464012noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3055499922775600843.post-9914766399095031052012-03-02T21:16:40.233+00:002012-03-02T21:16:40.233+00:00Phil, what a fantastic article. I think you sum u...Phil, what a fantastic article. I think you sum up perfectly the dilemmas facing most testers who want to specialise in skills, only to find that there is another 10 skills they needed yesterday, but still don't have.<br /><br />That's the joys of interacting will all aspects of a business, not that I would ever have it any other way.<br /><br />This ones a keeper, I be referencing it for sure. Thanks for sharing.Darren McMillanhttps://www.blogger.com/profile/15372641324627882128noreply@blogger.comtag:blogger.com,1999:blog-3055499922775600843.post-80836566289108308212012-02-29T18:27:12.224+00:002012-02-29T18:27:12.224+00:00That's all good advice, but the most important...That's all good advice, but the most important thing to learn IMO is how to get your whole dev team together to solve those problems - eg., experiment to find the best approach for your biz-facing tests that drive coding, the language to script them in, etc etc. It's good for us to know all that stuff (my team is about to read Design Patterns & discuss at a weekly brown bag), but most importantly, we have to have the skills to collaborate with all the other roles on our team and outside our team. We need the synergy and diverse skills to get the best solutions for each situation/team.Lisahttps://www.blogger.com/profile/10230090963033880060noreply@blogger.com