IoT validation end to end and Test Automation

The thesis was focused on a wide project that promote the use of the IoT technologies on the Automotive system, committed by a world leader in logistic services to the company Reply. This software product is mainly used by the fleet manager that has to control a lot of vehicles and so needs an easy and efficient way to program customized charging and preconditioning schedules for each vehicle. The Client has committed to the Company Reply the programmable part of the Telematic Control Unit of the vehicles. After the introduction about the testing process and the vehicle system structure, highlighting the communication protocol used by the component to exchange data and commands, the elaborate draws the attention on the validation of the software application deployed in the Telematic Control Unit carried out at Reply Company. The study about the right method to develop a great test environment combined with the analysis of the timeline of the testing process, allow to identify some criticality about the testing process waiting time. In the thesis project was proposed a strategy about the use of the waiting time between the detection of bugs and the re-test of them. This spare time was connected to well-planned test environment, indeed thanks to the use of specific automation tools is possible to create an environment comparable to the real world. This ensures to obtain a near instant feedback on code quality, due to fast and easy test execution, that allowing the team to identify and address issues promptly. The strategy consists in the use of this time for the automation of the entire test suite with the objective to validate the software faster and in exhaustive way in the future phases. This analysis was done according to the idea of implement the Continuous Integration (CI) and Continuous Delivery (CD) of the product in an agile environment. The agile methodology was used by a lot of company for the project development, because it ensures an improved software quality, indeed it involve the execution of no-regression testing. The no-regression testing process guarantees that existing features are not broken while developing new one. As for the use of automated testing in presence of the Agile Methodology environment, the conclusion was that it can significantly enhance software quality, accelerate development, and enable the release of more reliable and high-performing software. However, the automated testing must be well planned to avoid inefficiencies and costly maintenance, the code indeed must be reusable, and it is important to not underestimate the initial cost in terms of time resource for what concern staff training and test script development.