1052267 - [FxA] Create automated testcases to test username & password string validation for firefox accounts

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::UI Tests, defect, P3)

Comment 1

[Richard Pappalardo [:rpapa][:rpappalardo]]

Ideally, there should be only one way to do this kind of username/password string validation (rather than implement a unique test to do same for every single app).  I'm assuming the same would be true within the apps themselves, but I haven't looked into this.

Comment 2

[Geo Mealer [:geo] -- This account is inactive after 2015-07-07]

Taking this one, will talk with Richard to understand FxA dependencies

Comment 3

[Geo Mealer [:geo] -- This account is inactive after 2015-07-07]

After discussion:

For each place the FxA login or creation flow appears:

1) Create (if not already there) two flow tests, one valid and one invalid. These hit the Submit button and check the UI for appropriate handling.

2) Create tests for the client-side email validation. This should be a single automated test that iterates through a dataset (probably 100+ values) of email addresses built around the latest RFC (Unicode, variable number of subdomains, etc.) This dataset should be shared. These tests do *not* hit the Submit button, but test the button enabled/disabled behavior: "inject text, test button state at end, erase, next." Typing is undesirable due to speed. If the app otherwise behaves appropriately when text is set directly, we should do that.

3) Also, create a single test for character-by-character validation, checking enabled state after each character typed. This does need to use user actions character-by-character, since the behavior tracks that.

4) Create similar password tests. Only password constraint is length (must be >8) so dataset needs to include 7, 8, and 9 char values, as well as a range of character sets. Tests should look for * display, and red color on <8 char passwords. Bonus points for a string-length stress test.

Comment 4

[Geo Mealer [:geo] -- This account is inactive after 2015-07-07]

Taking on for implementation in Sprint 6