From 7b81330b3995ea0ff64dee289f8bb041fba9dcdf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lauri=20V=C3=B5sandi?= Date: Sun, 4 Apr 2021 12:03:22 +0000 Subject: [PATCH] Add test scenarios --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 44820a4..0e95546 100644 --- a/README.md +++ b/README.md @@ -5,11 +5,27 @@ pushes open door commands to door controllers. # Testing endpoints +For manually testing something like this might help: + ``` source .env curl -f http://doorboy.infra.k-space.ee:5000/allowed -H "KEY: $DOORBOY_SECRET" | md5sum ``` +# Test scenarios + +When updating doorboy proxy, members site or kdoorpi. +Verify follwing: + +* Swiping unknown card shows up as unknown, it can be claimed on members site and it immediately can be used after claiming +* Card enable/disable on members site works and has effect +* Opening door via buttons at https://members.k-space.ee/m/doorboy works and has effect +* Opening door via `/open-ground-door`, `/open-front-door` and `/open-back-door` commands in Slack channel #members works +* TODO: Keep door open via members site works and has effect + +When testing changes prefer using the *back* door and +use a brick or something to keep it open to prevent +interfering with other members entering and exiting. # Deploying