The README layout is a bit weird, with

1. Introduction (spelled wrong)
2. Test Plan Document sample
3. You should create a new section entitled Roadmap or QA Engineer Roadmap

• Add Twitter Icon
• Add text that says "Follow us on Twitter"
• Center the text

• A Checklist should be simple, but I like to reference many of the mnenonics when I test
• Add links to templates for help during test design.

Is your feature request related to a problem? Please describe.

Currently there is no javadoc description on any of the public classes, enums, interfaces, methods, constants.

Describe the solution you'd like

Need to add detailed description on all the public accessible objects and methods.

We only talk about those two things theoretically, and do not really show how to test them. We need (code) examples.

In 6.006 this semester, two students created an account named username and Username i.e. with the only change being the capitalization of the first letter. As a result they accidentally had two accounts each.

It should be forbidden to create an account with just case differences (maybe just lowercase all username inputs before putting into/querying from database?).

Description

Genuine, but stale HTTP requests should redirect to the logout resource. This behaviour will be equivalent to the one where users logout explicitly.

HTTP requests with no session information should still result in 403 responses.

Expected outcome

Improved UX in case of stale user sessions whereby users will be automatically redirected to the logout resource instead of