talberto-zz / tennis-bookings Goto Github PK

In the current configuration of the app, when a booking cannot be performed inmediately it's scheduled to be performed in the future. If several bookings are scheduled at the same instant t in the future, several threads will be started at the same time, using the same instance of the WebDriver. This cause all the bookings scheduled at that instant t to fail.

In the current implementation, some bookings are scheduled using Akka. The scheduled task is not persisted and therefore is lost if Dokku is restarted

Bookings that cannot be booked today must be handled differently from those that can be booked today. The former must be scheduled to try several times, at a regular intervals (2 mins), since the moment that we can book (9 am) minus a fixed amount of time (5 mins).

We must be able to follow up the state of the booking through some kind of entity attached to it (comments). Those comments will contain information about the different transitions that the booking will experience.

In order to diagnose better what wen't wrong, we will add more comments to a booking and a screenshot for every action performed by WebDriver