Automatisera testning av systemet

[patrik-pwned]

Story As a user (gäst, volontär, boställe) of the noq service i need to have working software available all the time so I can book room, manage, bookings and help other to book rooms.

Acceptance Criteria (checklist)

• [ ] There are suites of automatic integration tests that can be started manually and that run on the development server for now (and later also on staging server)
• [ ] Test suites for login, gäst booking and booking approval (bostället) are in place.
• [ ] Test suites for checkin and checkout are in place
• [ ] All test cases shall use the user interface for the noq app.

Acceptance Criteria (BDD)

AC1:

• We have automatic test case that tests that all user types can log in to the now app and get correct landing page

AC2:

• We have automatic test case that tests that a gäst can book a room

AC3:

• We have automatic test case that tests that a boställe can accept a gäst booking

AC3:

• We have automatic test case that tests that a boställe can checkin and check out a gäst

• [ ] Definition of Ready OK? Also called DoR, our generic process for checking if this is ready for start. See our Playbook here for details: https://docs.google.com/document/d/1ou6wr1sI9IJZaGGSMn_SJvFru5FJQKMDRZY16kBmx5Y/edit#heading=h.3rdcrjn

• [ ] Definition of Done OK? Also called DoD, our generic process for checking this is done in the right way. See our Playbook here for details: https://docs.google.com/document/d/1ou6wr1sI9IJZaGGSMn_SJvFru5FJQKMDRZY16kBmx5Y/edit#heading=h.23ckvvd

[LudvigErlandsson]

Denna måste brytas ned till något som är mer konkret! Känns mer som en EPIC nu!

[patrik-pwned]

Behöver mer input av vår stjärnutvecklare @jani-at-noq :D

[jani-at-noq]

I changed this to Epic, each AC should have it's own story. Size is large for all stories combined. We might also find out that the frontend code that we have created needs changes to enable testing (id's for elements might be too generic for example).