Update readyForTesting var even on Oobe.initialize() failure.

chrome/browser/resources/chromeos/login/login_shared.js

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /**
  * @fileoverview Common OOBE controller methods. This method is shared between
  * OOBE, login, and the lock screen. Add only methods that need to be shared
  * between all *three* screens here, as each additional method increases the
  * time it takes to show the lock screen.
  *
@@ skipping 264 matching lines @@
   /**
    * Restores input focus to currently selected pod.
    */
   Oobe.refocusCurrentPod = function() {
     DisplayManager.refocusCurrentPod();
   };
 
   /**
    * Some ForTesting APIs directly access to DOM. Because this script is loaded
    * in header, DOM tree may not be available at beginning.
-   * In DOMContentLoaded, this is marked to true, indicating ForTesting methods
-   * can be called.
+   * In DOMContentLoaded, after Oobe.initialize() is done, this is marked to
+   * true, indicating ForTesting methods can be called.
    * External script using ForTesting APIs should wait for this condition.
    * @type {boolean}
    */
   Oobe.readyForTesting = false;
 
   /**
    * Skip to login screen for telemetry.
    */
   Oobe.skipToLoginForTesting = function() {
     Oobe.disableSigninUI();
@@ skipping 145 matching lines @@
   return src instanceof HTMLTextAreaElement ||
          src instanceof HTMLInputElement &&
          /text|password|search/.test(src.type);
 });
 
 
 (function() {
   'use strict';
 
   document.addEventListener('DOMContentLoaded', function() {
-    Oobe.initialize();
-    Oobe.readyForTesting = true;
+    try {
+      Oobe.initialize();
+    } finally {
+      // TODO(crbug.com/712078): Do not set readyForTesting in case of that
+      // initialize() is failed. Currently, in some situation, initialize()
+      // raises an exception unexpectedly. It means testing APIs should not
+      // be called then. However, checking it here now causes bots failures
+      // unfortunately. So, as a short term workaround, here set
+      // readyForTesting even on failures, just to make test bots happy.
+      Oobe.readyForTesting = true;
+    }
   });
 
   // Install a global error handler so stack traces are included in logs.
   window.onerror = function(message, file, line, column, error) {
     console.error(error.stack);
   }
 })();