Create PowerButtonTestBase for three reasons:
(1) we don't have power_button_controller_unittest.cc, related test coverage are in lock_state_controller_unittest.cc and tablet_power_button_controller_unittest.cc
(2) we have more power button screenshot tests coming, from issue 712072
(3) reduce code lines: there are many common setup code and common util methods
I think this cleanup makes sense. Ideally I like the way each controller has its individual unit test file.
Also, I would like to move power_button_controller from ash/wm to ash/system/power/, for one reason:
(1) not like lock_state_controller, it observes powerd event, so it is more close to ash/system/power/ folder.
derat@, what do you think?
Comment 1 by derat@chromium.org
, Oct 4 2017