This policy is partially covered by the following automated browsertest tests:
- https://cs.chromium.org/chromium/src/chrome/browser/chromeos/policy/power_policy_browsertest.cc
- https://cs.chromium.org/chromium/src/chrome/browser/chromeos/policy/configuration_policy_handler_chromeos_unittest.cc

Fully testing this policy at the integration- or system-level presents some challenges, and will probably require Servo to simulate human activiy. The test shouldn't be written using browsertest, because the policy is only used in Chrome OS, and has dependencies on power management and display. I.e., too much would have to be mocked out, which would make it an ineffective and possibly invalid test.

To test that the scale is in effect, the test must first let the screen go dim (or off), then quickly perform a user activity before the device goes to sleep, to wake it up again. The scaling factor will then be in effect, and will remain in effect until the session ends. If the scale is set large (e.g., 200%), the test can detect that the next time the screen dims is twice as long as before. Unfortunately, since this test requires user interaction, it must use Servo to simulate an activity (e.g., key press, mouse click, mouse movement). The test also needs some way to determine that the display is on, dimmed, or off.

Releasing this back into the pool, to be done at a later date.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot