tag:blogger.com,1999:blog-1426281128647295476.post3910831009119191119..comments2009-08-06T11:23:49.611-05:00radihttp://www.blogger.com/profile/11459795773754260693radi@r-n-d.orgBlogger2125tag:blogger.com,1999:blog-1426281128647295476.post-37422873223949700252009-08-06T11:23:49.611-05:002009-08-06T11:23:49.611-05:00@Gabe: actually the idea is more toward providing the actual test case that can be plugged into the customer&#39;s testing automation right away.radihttp://www.blogger.com/profile/11459795773754260693noreply@blogger.comtag:blogger.com,1999:blog-1426281128647295476.post-69230848839549266672009-08-06T11:20:12.461-05:002009-08-06T11:20:12.461-05:00I&#39;m not a big fan of reusable test cases due to the poor success rates I&#39;ve seen so far. Almost every test org I&#39;ve been in tried at some point to create a super-duper-all-comprehensive automated testing framework by collecting testcases and parameterizing them so they could be executed against almost any target, only to realize that the parameter space is too huge to be practical. Translated in English, you&#39;ll always have to do some work to adapt testcases or their execution to the SUT. And in many cases you&#39;ll spend more times at filtering in/out testcases and adapting them to the SUT than if you started from scratch.<br /><br />In this sense, I&#39;m a big fun of bullet lists :-) A bunch of checklists works better than a robot.Gabehttp://www.blogger.com/profile/13958752731645145468noreply@blogger.com