Testing

This is a list of problems that have occurred that it would be nice to test for if we managed to put together a test suite one day. As mentioned in Github issue #914

• No internet - The script was actually written so that it wouldn't require internet access and usually works fine if the internet is down, but... we've had a few issues creep in over the years:
  • Kindle access via SSH - we added the ability for the script to SSH into a local kindle and change the screen, but if there was an internet problem or the kindle wasn't online this could cause the script to hang.
  • Slack updates - the script was updated to notify slack when people arrived, but this added a dependency on working internet, when the internet was down, the script would hang.
  • Solution - so far just disabling these actions, at some point it would be good to use something like Rabbit, beanstalk or MQTT so that the script could operate independently of these other - internet dependent - actions.
  • Testing - could we run the script in docker, a VM, or even a dedicated Pi that could have its internet disabled temporarily (probably from within the Pi even).
• Memory issues
  • Following some package updates and/or enabling the screen functionality the Pi started to run out of memory frequently.
  • Testing - If we had a dedicated test Pi we could perhaps have it running with all functionality of all the doormats and just have it see a card regularly to see if it died. Possibly it would automatically upgrade packages so that we would be forewarned of problems.