## 4 System Testing and Performance
### System Deployment in the Real Scenario  
The deployment of the whole system was carried out in an open space wide enough to perform experiments that would lead to valid, proven results that could be built to reach meaningful conclusions. An approach of incremental testing was followed, by which the team started performing lower key tests that, as the main objective, tested the behavior of the UAV itself, in case of software debugging of any kind, or if hardware refitting had to be done. The tests carried out have been listed as follows:  
1. Open-air flight under normal conditions: the first experiment was aimed at testing what the UAV performance looked like under the regular conditions expected to be used. Expectations were that it would perform with next to no issues. The results showed no significant trouble during the UAV flight: both the hardware and software used (Figure 9 shows the information obtained from the AutoPilot program used for flight missions before the UAV took off) regularly performed and no reprogramming or hardware mounting were required. 2. Landing under normal conditions: in this case, the experiment dealt with landing the drone without any damage or issue resulting from a normal landing, so that it couldbe used without any restriction in its usefulness. Expectations were that this task could be carried out without any problems; the results confirmed these expectations. 3. Open-air flight during unfavourable weather conditions: during the experiments that were carried out, it became evident that, in order to be truly useful, the UAV would have to operate under weather conditions likely to be unfavorable. While it is not expected that the UAVs will have to work in a hostile environment that would damage the electronics (heavy rain, electrical storms), the UAV should be usable enough to guarantee that an occasional, light rainfall or wind drifts will not result in serious damage to the UAV that will incapatte it to perform its duties. As described before, during the tests carried out with the UAV, it was proven that it could still work under such usage conditions, which had not been forecasted by the authors of this paper with enough importance during flight missions. Expectations were that the UAV would still be capable of normal flight under this kind of weather. While the results confirmed this, in terms of light rain and wind drifts, further testing was stopped in order to not damage the UAV. 4. Landing under unfavourable weather conditions: the UAV had to land in unfavourable weather conditions to prove that it could be recovered from flight missions without any problems. Expectations (the UAV could be recovered without having taken damage after the flight) were met again in this experiment. Once it was proven that positive results had been obtained from the experiments, further flights were performed with the vehicle mounting the MDAS, so that not only the flight of the UAV and the MDAS combined could be tested, but also to collect information regarding power signals and their performance. Since the UAV used had already been successfully tested, there were several additional experiments carried out in order to test the whole infrastructure, along with the software developed for the proposal:  
1. Information collection from mobile network signals: this is the main purpose of the system built and the reason why all the measurements are taken. In this case, the experiments were carried out to collect information related to 4G Long-Term Evolution (LTE) coverage in the area of testing and experimentation. The experiment consisted of, once the MDAS had been mounted to the UAV, setting the latter to fly and cover a large  
Figure 9: ArduPilot Mission Planner tool during one of the experiments. three-dimensional area with a speed and manoeuvrability that could not effectively be matched by a team of human operators. Expectations before performing this experiment contemplated the possibility of obtaining accurate information regarding mobile network signals.