Transformation of manual test cases into test automation
The brief
As part of maintenance activities for a financial services provider’s data centre, the existing manual test cases were to be converted into tests that could be performed automatically. The basis for test automation was an in-house development created by the customer. After the conversion, the ratio of automated to manual test cases was to be 80 to 20.
Our approach
In the first step, we familiarised ourselves with the existing in-house development and analysed existing test cases from other business areas. Using this as a basis, we transferred the concept and methodology of the software to our business area and gradually converted the existing test cases into test automation logic. At the same time, the corresponding test cases were revised and updated. The biggest challenge lay in the different applications and requirements. There were test cases for the different applications, including for internal sales, field sales and, in addition, for the website for direct customer business. Here, all platforms had to be considered with various test procedures.
The solution and key benefits
Our many years of testing experience and our expertise in test management ensured that the existing test cases were quickly transformed and updated. In addition, new test cases were created, the total number of test cases was increased, and the processing and turnaround times for maintenance tests for each release deployment were reduced. It would have been possible to transform all test cases into test automation, but this also carries risks. Only manual testing can reveal anomalies in the design and layout in terms of ‘look and feel’. Furthermore, some test cases require a great deal of effort to maintain the test data, so that manual execution is more resource-efficient than full test automation.
Conclusion:
The introduction and implementation of test automation is sensible and necessary, but it should only be used as a support tool and chosen with care. A blind, comprehensive transformation is neither effective nor desirable; instead, it should be introduced with experience and in-depth expertise.