Make sure to display an errors that occur during the chrome sign in process
to the user as a bubble on the NTP.
BUG=81265
TEST=Gaia related errors, such as incorrect email, password and/or otp are handled by the gaia sign in page itself. These errors are reported just like on any gaia sign in attempt.
Errors that occur after sign in, such as an account already connected with another profile, or an account prohibited by policy, and so on are displayed as bubbles on the ntp. Test scenarios that should be considered:
- all sign in access points: first run, ntp, wrench menu, settings, and one-click sin in
- use account with and without 2-factor enabled
- scenarios where you type the correct password and/or otp the first time, incorrect once and correct the second time, incorrect twice and correct the third time. Its important to test with multiple failures in a row before typing the password correctly, but I would't bother past 3 failed attempts followed by a successful attempt
- try closing the tab used for the sign in before actually signing in. Or simply navigate to another page and start browsing with it
- on the settings page, make sure that the advanced configuration dialog works as expected when signed in. Try it multiple times, changing the options and saving or cancelling
- open two windows, and a settings page in each one. Try to sign in with one while clicking on buttons on the other
- make sure that one-click behaviour is not changed. That is, it should only be offered once per profile. Also make sure that the four other access points do continue to be offered after having used one-click sign in
- make sure that rejected emails wrt one-click sign in do not prohibit that account from signing in with the four other access points
- create a second profile and do the same tests. in particular, try to use the same account as the first profile (it should not be allowed)
Note that gaia currently does not support sign in for chrome using "re-auth". That is, if you see a sign in page where the email address is already filled in and unchangeable, then this is a re-auth. This will land in gaia soon. How does this affect testing? In the following scenario:
- sign in to chrome once (for example, with first run)
- go to settings and disconnect the profile
- sign in to chrome again (for exaample, from the settings page)
In this case, you will see a re-auth screen. To proceed, click the sign out link at the bottom of the form and then sign in again.
Review URL: https://chromiumcodereview.appspot.com/11411267
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171190 0039d316-1c4b-4281-b951-d872f2087c98
11 files changed
