Settings People Revamp: Add tests for ChromeOS Change Picture.

chrome/browser/resources/settings/people_page/change_picture.js

Index: chrome/browser/resources/settings/people_page/change_picture.js
diff --git a/chrome/browser/resources/settings/people_page/change_picture.js b/chrome/browser/resources/settings/people_page/change_picture.js
index 5fe931b3e17d7af1aa6931e1980dd019a396f92a..3127373a7654abd7eb6e59a1b28497c8f45f3f12 100644
--- a/chrome/browser/resources/settings/people_page/change_picture.js
+++ b/chrome/browser/resources/settings/people_page/change_picture.js
@@ -2,6 +2,17 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
+cr.define('settings_test', function() {
+  var changePictureOptions = settings_test.changePictureOptions || {
+    /**
+     * True if property changes should fire events for testing purposes.
+     * @type {boolean}
+     */
+    notifyPropertyChangesForTest: false,
+  };
+  return {changePictureOptions: changePictureOptions};
+});

[Dan Beam, 2016/03/16 17:22:29]

why can't this just be

cr.exportPath('settings_test');

OR

cr.exportPath('settings_test').changePictureNotifyForTest = false;

the difference between cr.define() and cr.exportPath() is that cr.define() is
more useful when an inner scope is required for bookkeeping.  in a case as
simple as this, cr.exportPath() may be preferred.

+
 /**
  * @fileoverview
  * 'settings-change-picture' is the settings subpage containing controls to
@@ -22,7 +33,10 @@ Polymer({
      * The currently selected profile image URL. May be a data URL.
      * @private {string}
      */
-    selectedImageUrl_: String,
+    selectedImageUrl_: {
+      type: String,
+      notify: settings_test.changePictureOptions.notifyPropertyChangesForTest,
+    },
 
     /**
      * The url of the 'old' image, which is the existing image sourced from