Improvement of Test Automation
Räsänen, Timo (2013)
Räsänen, Timo
Metropolia Ammattikorkeakoulu
2013
All rights reserved
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2013053011861
https://urn.fi/URN:NBN:fi:amk-2013053011861
Tiivistelmä
The purpose for this study was to find out how to ensure that the automated testing of MME in the Network Verification will continue smooth and reliable while using the in-house developed test automation framework. The goal of this thesis was to reveal the reasons of the currently challenging situation and to find the key elements to be improved in the MME testing carried by the test automation. Also a reason for the study was to get solutions as to how to change the current procedures and ways to perform the automated testing to fill better the requirements of Network Verification.
The study was carried out by studying the currently used test automation framework and its utilization. That knowledge was then compared to the best practices of the existing test automation methods to find out what should be changed to get the performance and the quality of test automation on the right level. One of the main reasons for this situation is that the fast expansion of the test tool usage and the rapid increase of test coverage with insufficient resources have left the some features, e.g. documentation, lagging behind and now it slows down the debugging and therefore consumes the time resources from further development. One of the proposed solutions for this particular issue is a requirement to add comments on basically every script and code to improve knowledge of the test case to anyone working with it. Some other proposals offer tools on how to decrease the testing time by changing the method
The study was carried out by studying the currently used test automation framework and its utilization. That knowledge was then compared to the best practices of the existing test automation methods to find out what should be changed to get the performance and the quality of test automation on the right level. One of the main reasons for this situation is that the fast expansion of the test tool usage and the rapid increase of test coverage with insufficient resources have left the some features, e.g. documentation, lagging behind and now it slows down the debugging and therefore consumes the time resources from further development. One of the proposed solutions for this particular issue is a requirement to add comments on basically every script and code to improve knowledge of the test case to anyone working with it. Some other proposals offer tools on how to decrease the testing time by changing the method