Test Report:
Due to the fact that it is not possible to use the BPMN-model that we have done with the camunda modeler inside the activiti framework, we had to remodel the BPMN-model inside the activiti modeler. The drawback with this was, that the activiti framework does not support artefacts, like databases or general data objects. Therefore, we could not model these. We have to use other methods, like java fields in entities, to store these artefacts while using the framework. While modeling, we had to double check, if all edges were drawn correctly, because the eclipse plugin of the activiti modeler is not stable all the time.
We had to outsource the BPMN process into a seperate thread so we could handle the http response concurrently. Otherwise it would have been possible, that the user would have got a timeout in the browser window, while the process is still running.
The google api to get the distance/duration between the hospital and the location gave us a few problems. Also, it was not possible to get the live traffic updates from google, we just have normal routing now. A problem was that we always got an 400 http error, which prevented us from further testing the other tasks. This is so, because each task has to get completed successfully before the flow of the model can continue. Otherwise, some tasks will never trigger and we can't test them. This took some time, because each task before a certain task has to get done correct to enable debugging afterwards.
Another problem was the web ui that was not served correctly by our spring boot - activiti combination, therefore we had to find another solution to host it for our students.
