<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by John J. Miller: 1. That your product testing needs are sufficiently complex, detailed or time-sensitive that they can't be handled adequately with manual means.
2. The costs involved in acquiring the tools.
3. Your ability to actually apply those tools efficiently.
4. The level of support you might receive from your development groups in terms of application-consistency and direct support for automation needs.
5. The level of support from management for such an effort.
6. The realization that automation is a full software development effort in itself.
I think 6. is the key. To expand on this a bit:
6.a) Automated test case development requires a thorough understanding of the SUT (system under test) and test tool.
6.b) As is the case for all software, maintenance costs for automated test cases will grow over time and must be planned for.
Tool changes or SUT changes will impact test
case maintenance costs. For the SUT, the changes could be functional changes or configuration changes.
Testability = 1/complexity