Milestone 16: Quality Assurance¶
Sunday, April 21
Each team will get a copy of another team’s project and do extensive testing of it. You will be added to the other team’s github project as a read-only member which will let you create new Issues on their repo. Add all the bugs you find on the project as github issues. The other team will label them.
A-teams will find at least a dozen bugs, typically, and clearly explain how to reproduce the bug.
To capture screenshots, videos, and make animated gifs, I recommend monosnap. Free for macs and windows.
When testing the other group’s project you need to:
- Add every bug you find to their Issues list. Use screenshots whenever useful. Explain clearly how to reproduce the problem.
- When you are done testing, tell the other team.
When being tested you will assign labels to each issue the testers submit. Namely:
- Add the qa label to all their Issues. This is a new label to help us distinguish the other teams’ Issues from yours.
- If it is a bug, give it the bug label. Add it to the 1.0 Milestone.
- If it is not exactly a bug, but something that really should be added, you can add an issue about it with the enhancement label.
- If it is a duplicate of an existing Issue, write a comment pointing to the Issue you want to keep, add the built-in duplicate label and close it.
- If you decide that fixing it is outside the scope of the project then add the wontfix label, explain why, and close it.
Grade is 100 minus the total points lost, with minimum of 0. See grading scale in Syllabus. Points lost are:
- No enough bugs reported. 0 100 points
- Bug reports are badly written or unclear. 0 80 points
- Did not label the incoming bug reports correctly. 0 20 points