Decide what needs to be tested in the frontend
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
We need to decide what we need to test for our Web UI. This is important as we want to make sure tests are written and passing so we can ensure our code is working and future changes don't break functionality.
How are you going to acheive the goal or solve the problem?
Read the Angular guide for testing the type of form we are using.
What will be produced as a result of this effort and where will it live on GitLab?
- Links to resources.
- A discussion about which items to test in our Web UI.
Give a justification of weight or due date.
This will take some time to figure out what we can test in the frontend and deciding what needs to be tested.
Who will do it, and what will they do?
Two members of the UpdateGuest team.