1. Do: Know what you get!
In practice, companies that measure the success of their test automation only in terms of the highest possible number of test cases, are often confronted with redundancies of more than 60 % in their test portfolio and a risk coverage of less than 40 %. Thus, time and resources are bound without any significant success being recorded.
Plan the use of automated testing strategically and set measurable targets that are geared towards risk coverage. Even with a small number of properly installed test cases, you can achieve a very high risk level.
2. Don’t: Raise unrealistic expectations
Even after your test architecture and cases are established, automated testing is not running itself. Your portfolio needs to be maintained, new requirements have to be included and implemented. At Wiener Städtische, the number of test cases were reduced, while at the same time risk coverage increased. The customer benefits from the use of more Tosca functions: with Tosca's module-based approach, maintenance can be kept to a minimum.
3. Do: Set priorities – have the right test cases!
In practice, functions that are easy to test are often covered by a large number of tests without taking the contribution to quality assurance into account. This leads to a high test number in certain areas, while other, possibly more important functions, are badly tested - so there is an overall low risk coverage.
Also, make sure that you do not create redundancies in your portfolio and that you use a sophisticated methodology to define test cases. The combinational method of linear expansion supports the generation of test cases at the push of a button. They set "smooth runners" and then test them with all possible variants. To maximize the risk profile of each test case.
4. Don’t: Use sprawling expenses for test data generation
The basis for successful automated testing is a professional test data management, in which data required for tests are provided and managed by a tool. At Wiener Städtische Versicherung, the effort to prepare test cases was massively reduced by consistently planning, generating, providing and managing test data.
5. Do: Employ specialists and use appropriate tools
Establishing knowledge and skills in one's own company is essential to remain successful in the long term. Wiener Städtische decided to evaluate testing with professional support from Qualysoft and Tricentis and to train their own team with the help of experts in practice. The teams developed sets of machine test cases that were immediately applied. In doing so, the insurance team benefited from the know-how transfer and the transfer of input-output ratio "benchmarks" and will be able to support, maintain and further develop the project in the future.
6. Don’t: Make maintenance complicated
To ensure that the risk coverage does not decrease over time, and that the results are of high significance, the test cases must be kept up to date and maintained. Factors such as the neglect of test portfolio management, the uneven distribution of test cases via processes and applications as well as redundancies make maintenance more difficult and time-consuming. If your software testing is already professional from the outset, you can concentrate on the essentials in daily operation.
7. Do: Support learning and networking
Using the selected methodology, business users can be integrated into the definition of test cases in a time-saving and resource-conserving manner. In the course of the test definition, business processes are presented transparently across all areas and clearly separated between specialist and technical topics. This allows IT and technical departments to work together more efficiently and quickly.
8. Don’t: Set areas of application too restrictive
Think beyond individual applications and test end-to-end processes. Modern test methods allow business processes to be examined beyond application limits – not only to test an isolate single application but to implement a whole test case across all applications.
9. Do: Communicate results and successes
Automatic software testing can be compared with insurances - if everything works smoothly, people don’t talk about it – only when a mistake has happened, the issue draws the attention. Therefore it is important to present meaningful key figures in the company and to communicate successes proactively in order to keep the commitment high.
10. Don’t: Neglect further development
You should constantly develop and prepare your test case portfolio for new requirements. So you can ensure that the risk coverage remains high and that the functions of your applications work smoothly in the long term – even if you want to develop and implement innovations quickly.