chromeos: Makes AshTestBase/Helper target mash when appropriate

ash/mus/test/wm_test_helper.cc

Index: ash/mus/test/wm_test_helper.cc
diff --git a/ash/mus/test/wm_test_helper.cc b/ash/mus/test/wm_test_helper.cc
index dc94727b60c313fa73f5433223b68c31db23957f..36dbefa8b70943876901437f25214c79bdedf37f 100644
--- a/ash/mus/test/wm_test_helper.cc
+++ b/ash/mus/test/wm_test_helper.cc
@@ -84,6 +84,9 @@ WmTestHelper::~WmTestHelper() {
 }
 
 void WmTestHelper::Init() {
+  // General pattern is most places don't uninitialize, so we have to explicitly

[msw, 2017/02/19 21:49:20]

Can you rephrase and clarify this comment? ie. The general pattern of what? test
fixtures? WmTestBase is the only user of this class, afaict, and its TearDown
override resets the WmTestHelper instance, which already calls uninitialize, so
I'm a bit confused.

[sky, 2017/02/21 17:06:50]

I tried improving the comment. Any better?

[msw, 2017/02/22 06:25:48]

Yes, that makes more sense now.

+  // uninitialize before initializing.
+  ui::test::MaterialDesignControllerTestAPI::Uninitialize();
   ui::MaterialDesignController::Initialize();
 
   views_delegate_ = base::MakeUnique<views::TestViewsDelegate>();