Why do we need a system that will assess the benefits of introducing the question more rhetorical than practical, but still try to formalize the reasons why the study of the efficacy can be considered an integral task in the selection, implementation and use of test automation.
In fact, often the choice of test automation tools, especially its estimated operational imperative: that is chosen tool or a product line that will perform the necessary set of tests that can be performed manually (load and stress tests) and with due automates the process of manual (Functional and regression) testing. If the cost of funds, which decided to get fit in costs for a specific project (such as highly specialized means of generating test data or more advanced tools from little known companies that are just entering the market) the question of return on investment is not very important. However, the acquisition range of tools, which cost can often exceed the cost of a development project, the embedding is treated as capital investments in production and subject to the same laws as the equipment or computer technology. Taking into account that the licensing policy of many companies provides for the extension of licenses for products annually, the cost of equipment becomes an important criterion, not only during the selection tool, but also during its operation and future use. It is not excluded that after seeing the bill for a license for next year, the company or investors will want to assess how effectively the funds allocated were used to automate testing. There is a need for a mechanism estimates savings of man-hours.
As a variant of such an evaluation can be considered a small document, which is being developed at the time of launch automation system and filled with the project manager or supervisor direction as the introduction and use of the tool. The document structure is simple: record an issue which was resolved with a tool or a description of the work situation in which using the tool were savings of resources and assessment of man-hours of time that was saved. Knowing the value of person-hours in a specific project, you can effortlessly calculate the real cost savings of resources. Also do not forget about the improvements in the development process, which can not be directly assessed, but must also be taken into account when developing the document. For example using testing tool able to simulate system performance under a load of 100-200 users. The real savings is that it was not necessary to carry out such time-consuming testing, but to estimate man-hours of developers and testers it is difficult.
Thus, the analysis of systems test automation is not limited to prior to purchasing analysis. Of course, effectively can only be used a tool that has been chosen according to demands and satisfies the business needs of the team testing and development. But also its subsequent evaluation, so to speak companion, work analysis, can also be very useful when it is necessary to assess the real benefits that have been made introducing and using test automation.