Add a group policy for hardware acceleration.

chrome/browser/policy/policy_browsertest.cc

Index: chrome/browser/policy/policy_browsertest.cc
diff --git a/chrome/browser/policy/policy_browsertest.cc b/chrome/browser/policy/policy_browsertest.cc
index 8c20f2c763740abd8bdeb524b3c83507b1df758c..940b1c683b212d077a66be234bff35e482b7094f 100644
--- a/chrome/browser/policy/policy_browsertest.cc
+++ b/chrome/browser/policy/policy_browsertest.cc
@@ -3838,4 +3838,31 @@ IN_PROC_BROWSER_TEST_F(PolicyTest, NativeMessagingWhitelist) {
 
 #endif  // !defined(CHROME_OS)
 
+
+#if !defined(OS_CHROMEOS) && !defined(OS_ANDROID)
+// Sets the hardware acceleration mode policy before the browser is started.
+class HardwareAccelerationModePolicyTest : public PolicyTest {
+ public:
+  HardwareAccelerationModePolicyTest() {}
+
+  void SetUpInProcessBrowserTestFixture() override {
+    PolicyTest::SetUpInProcessBrowserTestFixture();
+    PolicyMap policies;
+    policies.Set(key::kHardwareAccelerationModeEnabled,
+                 POLICY_LEVEL_MANDATORY,
+                 POLICY_SCOPE_USER,
+                 new base::FundamentalValue(false),
+                 NULL);
+    provider_.UpdateChromePolicy(policies);
+  }
+};
+
+IN_PROC_BROWSER_TEST_F(HardwareAccelerationModePolicyTest,

[Andrew T Wilson (Slow), 2015/07/16 09:59:55]

What about the true case? Should we test that hardware acceleration defaults to
true, or at least setting it explicitly to true leaves it enabled?

[Zhenyao Mo, 2015/07/16 18:06:31]

In the first CL I did test that, but unfortunately GPU can just be blacklisted,
so if we leave this to true or unset, it is not guaranteed the
GpuAccessAllowed() returns true.  That's why I removed the test case.

+                       HardwareAccelerationDisabled) {
+  // Verifies that hardware acceleration can be disabled with policy.
+  EXPECT_FALSE(
+      content::GpuDataManager::GetInstance()->GpuAccessAllowed(nullptr));
+}
+#endif  // !defined(OS_CHROMEOS) && !defined(OS_ANDROID)
+
 }  // namespace policy