Form testing: Registration

[enewe101]

Test client side validation on the username:

• when a user types in a username that is available, the word "available" appears below the field
• when a user types in ... unavailable ... "unavailable" appears ...
• when a user types some stuff in the username field, then clears it, nothing appears below the field
• when a user types in a username that has symbols ('!#@%'), a warning appears below the field

Test client side validation of passwords

• in the first password field, if a password is typed that's less than 8 characters, "too short" appears
• in the first password, if the user types some stuff then clears it, no hint is displayed
• if the first password doesn't match the second password, a hint is displayed "doesn't match"
• if the passwords don't match, but one of them is blank, the hint isn't displayed

Test server side validation on the username:

• If the username is empty, the user is not registered, the form is displayed with an error message "required"
• if the username has symbols, user not registered, form displays with error
• if username is taken, user not registered, form displays error

Test server side validation of the passwords

• submitting the form with non-matching passwords, user is not registered, form displayed with error
• submitting the form with passwords that are too short, user is not registered, form displayed with error

Test server side validation of email

• submitting the form with an email that is already in use by a user causes the "did you already registner" page to be shown.

[dimitrovs]

How do we prioritize issues in Github? Is there a ranking system?

[enewe101]

hey, I don't know whether ther is. That would be useful. We could make labels for that?

[enewe101]

How about the label "critical" which we use for the highest priority stuff. Everything is assumed to be at normal priority unless labeled critical.

[enewe101]

@verolag I've started a test on the branch register_test. Go ahead and git pull --all, then git checkout register_test, and have a look in ~/src/test.py. You'll see a class called RegistrationFormTest.

I also decided update the wiki entry for writing tests. I think you'll find it helpful to get an idea of how to approach writing tests and how to manipulate the browser using Selenium.

One thing -- Among all the cases to test listed above, there are cases where a notification should disappear if the text in a field is cleared:

• when a user types some stuff in the username field, then clears it, nothing appears below the field
• in the first password, if the user types some stuff then clears it, no hint is displayed
• if the passwords don't match, but one of them is blank, the hint isn't displayed

For some reason, when Selenium enters non-printable characters (such as a backspace), firefox doesn't register a key event, and that means that the notification doesn't clear (even though it works when a real user does it). So, basically, those conditions can't be tested, but that's no big deal.

Post if you run into any issues!