Homework 7: Evaluate (canceled)

Now that every team has launched, it's time to find out whether these applications are functionally correct. Your job in this homework is to find failures in all of the other team's applications. You'll follow the scale as described in Homework 7:

• Major. Functionality cannot be used to accomplish the intended task. (Remember that this includes usability issues that prevented someone from being able to understand how to accomplish the intended task).
• Minor. Functionality can be used to accomplish the intended task, but requires a workaround or understanding a design choice with poor usability to be used successfully.

You can find the application URLs listed on each team's GitHub repository page. For each one, use the application, trying all of its major features, filing bugs in the team's GitHub Issues page for each problem you find, marking their severity with the labels above. Expect to spend at least 10 minutes with each application, for just over 1 hour of testing.

To structure your testing, consider using the Black Box Testing Links to an external site. strategy in HowToo. It gives you a basic outline for how to test systematically and document your findings.

Read the existing list of issues before you file your bug to avoid filing duplicate reports. We won't give credit for issues that a team deems a duplicate. This is an incentive to avoid duplicates, to test thoroughly, and to test early. (When you mark something a duplicate, make sure you're not marking the first submitter's a duplicate—they're the one that deserves credit).

Note that you can fix defects reported by others as soon as they're reported; you don't have to wait until after the evaluation period. Schedule time after the release deadline to triage, diagnose, and repair issues to minimize the potential for other major defects being reported.

Grading criteria

This homework is worth 5 points and is individually scored. Unlike all previous homeworks, this is an individual assignment. You'll get 1 points for each high quality issue. High quality issues include:

• Unambiguous reproduction steps
• A clear description of the failure
• Clear rationale for why the issue is problematic (especially for reports that concern usability rather than functionality)
• Not deemed a duplicate by the team.

To get credit for this assignment, submit a list of links to all of your submitted GitHub issues you want credit for. We'll grade all of them, giving you the highest possible score. This is your incentive to submit as many high quality issues as you can.