-
Notifications
You must be signed in to change notification settings - Fork 2
QA User Testing Protocol
(This is written by me (CatQueen/Grace) so ping me on discord if you have questions!)
This is for testing the game from an actual users point of view. This means we want to use the live site on the actual browsers and devices our users will be playing on. Things may work in your local dev build but not work as expected once live.
All testing is to be on the live site: https://cardsofcarousal.com/
Multiple people can (and should) work on each test case as they require testing on multiple different browser and devices.
Feel free to try and break it in ways that are not included in your test case as well (I'm sure I did not think of everything)!
There are 3 columns:
1. Test Cases: These are test cases linked to user stories for components that have been made since the beginning of COC. They currently require testing on:
- Desktop (Safari, FireFox, Chrome)
- iOS device (Safari, Chrome)
- Android (Chrome)
2. Tests in Progress:
I have created tags: Android Testing Needed, iOS Testing Needed, Desktop Testing Needed, Accessibility Testing Needed. Once you complete all the test for one of the above please remove the corresponding tag and move it into the Tests In Progress column.
3. All Tests Complete:
If you are the person to complete the final checkmarks on a test ticket, move it to this column!
Please keep track of the following as you test in the event you find a bug:
- What data you input/the output (if data input is necessary for your test scenario)
- The steps taken during the test
- What browser & device are being used
- Screenshot/video screen capture for the bug ticket.
If you find a bug follow the Bug Protocol below!
Use this [Bug Issue Template](link to template) to create an issue in the the Bugs/Refactor Kanban under the Triage column with the correct tags.
If there are multiple unique bugs per test case make one bug ticket per issue. If you find the same issue on multiple browsers on the SAME device, you can make one bug ticket and note all browsers it occurs in.