BLE localisation automated feature testing
Versickas, Aleksandras (2023)
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2023060521626
https://urn.fi/URN:NBN:fi:amk-2023060521626
Tiivistelmä
The objective of the project was to make an automated software feature tester available at all times and used everytime a developer updates the Bluetooth low energy localization software used by Onsemi RSL15 boards.
The project was made in order to improve the quality of the software delivered everytime an update is made and to reduce the risk of software failures by informing the developers of possible flaws automatically and preventing them from releasing the update.
The making of the tester was divided into several specific parts but it is possible to identify two major parts which are the creation of the tests and the automation of their execution.
A significant learning curve was needed to proceed with the project because of the use of many technologies, many trials were made before getting an acceptable result.
At the end the tester was operational and used by the developers. The quality and stability of the software was increased by reporting the results of the features tests on many different use cases automatically before each update is released letting the developers solve the issues if there is some.
It is necessary to know that as the software is updated and presents new features the tester needs to be updated to test the new features as well in the future which adds some maintenance needed to the whole project.
The project was made in order to improve the quality of the software delivered everytime an update is made and to reduce the risk of software failures by informing the developers of possible flaws automatically and preventing them from releasing the update.
The making of the tester was divided into several specific parts but it is possible to identify two major parts which are the creation of the tests and the automation of their execution.
A significant learning curve was needed to proceed with the project because of the use of many technologies, many trials were made before getting an acceptable result.
At the end the tester was operational and used by the developers. The quality and stability of the software was increased by reporting the results of the features tests on many different use cases automatically before each update is released letting the developers solve the issues if there is some.
It is necessary to know that as the software is updated and presents new features the tester needs to be updated to test the new features as well in the future which adds some maintenance needed to the whole project.