Automated tests in automotive solutions
Soukka, Kalle (2023)
2023
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2023060923153
https://urn.fi/URN:NBN:fi:amk-2023060923153
Tiivistelmä
Opinnäytetyössä käydään läpi 3kk kestänyt testiautomaatio asiakasprojekti autoteollisuuden asiakkaalle. Työn tavoitteina oli tehdä automatisoituja testejä asiakkaan tuottelle ja etsiä haavoittuvaisuuksia stabiilisuudessa. This thesis is a look into a customer project in doing automated tests in automotive software. It details a time period of three months during which the project took place. This project was done mostly remotely by using remote computer methodologies to control the testing devices.
Testing was done using Profilence company Tau analysis tool and the system tested was an Android based. The results of tests were saved in cloud and then analysed so that the customer would get a picture of the problems appearing in the software.
Throughout the project there were also many different changes to both the software and the hardware and new tests, and test methodologies had to be created for these. There was also a lot of maintenance that had to be done for the devices throughout the project. The use of devices continuously encountered many different problems during the test runs and new software and hardware parts needed new implementations of testing.
Analysing shows that the stability of the software was improved in many different fields of the software. While all the customer requirements were not achieved, the software was improved.
Testing was done using Profilence company Tau analysis tool and the system tested was an Android based. The results of tests were saved in cloud and then analysed so that the customer would get a picture of the problems appearing in the software.
Throughout the project there were also many different changes to both the software and the hardware and new tests, and test methodologies had to be created for these. There was also a lot of maintenance that had to be done for the devices throughout the project. The use of devices continuously encountered many different problems during the test runs and new software and hardware parts needed new implementations of testing.
Analysing shows that the stability of the software was improved in many different fields of the software. While all the customer requirements were not achieved, the software was improved.