Disable/enable echo for enterprise device.

chrome/test/data/extensions/api_test/echo/component_extension/test.js

Index: chrome/test/data/extensions/api_test/echo/component_extension/test.js
diff --git a/chrome/test/data/extensions/api_test/echo/component_extension/test.js b/chrome/test/data/extensions/api_test/echo/component_extension/test.js
index c364d86a9c85d12d28795d3337d070f2781e2a92..b37c2643c3c1b55ef612c984f7b9109e24e0d475 100644
--- a/chrome/test/data/extensions/api_test/echo/component_extension/test.js
+++ b/chrome/test/data/extensions/api_test/echo/component_extension/test.js
@@ -23,5 +23,9 @@ chrome.test.runTests([
         chrome.test.callbackPass(function(result) {
       chrome.test.assertTrue(result == '');
     }));
+    chrome.echoPrivate.isEchoDisabled(
+        chrome.test.callbackPass(function(result) {
+      chrome.test.assertFalse(result);
+    }));

[Mattias Nissler (ping if slow), 2013/02/04 09:06:19]

You should also write a browser_test that checks whether the extension API
function(s) affected by the policy behave as expected if the policy is set. See
chrome/browser/policy/policy_browsertest.cc for examples.

[oscarpan, 2013/02/05 00:17:47]

Working on it.
On 2013/02/04 09:06:19, Mattias Nissler wrote:

   }
 ]);