Testing

Due to our heavy dependency on external APIs like Slack and GitHub it's hard for us to write comprehensive tests, but we have a few unit tests. Should you wish to do a full end-to-end test, the safest way to do so at the moment is to temporarily stop the Rocket production container and deploy Rocket on your personal computer the exact same way you would in production, with all the same credentials. This works because Slack messages are sent to Rocket via a websocket that is initiated by Rocket, so Rocket doesn't need a public IP to receive Slack messages. This way you'll also have free-reign over a throw-away Postgres container that you're running locally, so you don't have to worry about messing up any important data. You should, however, be careful with GitHub integration because Rocket will still be able to manage the UBC Launch Pad organization on GitHub while you're running it locally.