| || |
What Should be Considered when Evaluating a Test Tool?
What Should be Considered when Evaluating a Test Tool and why? Thanks.
Re: What Should be Considered when Evaluating a Test Tool?
1. Your understanding of the test needs of your product. (Any tool will get you there if you don't know where to go.)
2. A series of 30-day eval's of several promising tool candidates that comform to your initially stated needs. Note: your 'needs' will be changed and substantially clarified by this effort. (New territory requires some tentative exploration.)
3. A skill set assessment and work-philosophy assessment of your groups' ability to effectively apply each of the candidate tools. (It it doesn't fit; you won't be happy or productive with it no matter how much the next guy likes it or how much money you 'saved'.)
4. A sense of certainty regarding management's and engineering's support for such an effort. (Politics. You can't go it alone and be effective at it unless that cooperation and support are acknowledged and made available from controlling external influences. Without it, there be dragons!)
5. A realization by yourself, management and engineering, that automated test development IS a full time parallel, equivalent effort to that of product development. (It ain't as easy as it seems and there ain't no free lunch.)