Add error messsage bubble flag for tests.

chrome/browser/resources/login/display_manager.js

Index: chrome/browser/resources/login/display_manager.js
diff --git a/chrome/browser/resources/login/display_manager.js b/chrome/browser/resources/login/display_manager.js
index 3644beb1321bd8ec27b9ef14fdf8739d24852fb2..d6112674ce1f56e8521d6d8d5283b08d56bdbcf8 100644
--- a/chrome/browser/resources/login/display_manager.js
+++ b/chrome/browser/resources/login/display_manager.js
@@ -178,6 +178,11 @@ cr.define('cr.ui.login', function() {
      */
     displayType_: DISPLAY_TYPE.UNKNOWN,
 
+    /**
+     * Error message (bubble) was shown. This is checked in tests.
+     */
+    errorMessageWasShownForTesting_: false,

[achuithb, 2014/05/07 20:38:32]

We have a number of testing apis here:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/res...

Should we add this to login_common.js, or is this the best place for this? We
may need to set more variables in the future for testing.

[Alexander Alekseev, 2014/05/07 21:00:16]

I think the less code "for testing only" we add to production code,
the less complex code we get. Keeping this flag close to the set/clear code for
it is probably easier to support. So I would probably leave it here.

[achuithb, 2014/05/07 21:10:03]

sg

+
     get displayType() {
       return this.displayType_;
     },
@@ -876,8 +881,10 @@ cr.define('cr.ui.login', function() {
     }
 
     var currentScreen = Oobe.getInstance().currentScreen;
-    if (currentScreen && typeof currentScreen.showErrorBubble === 'function')
+    if (currentScreen && typeof currentScreen.showErrorBubble === 'function') {
       currentScreen.showErrorBubble(loginAttempts, error);
+      this.errorMessageWasShownForTesting_ = true;
+    }
   };
 
   /**
@@ -907,6 +914,7 @@ cr.define('cr.ui.login', function() {
    */
   DisplayManager.clearErrors = function() {
     $('bubble').hide();
+    this.errorMessageWasShownForTesting_ = false;
   };
 
   /**