mus: Add views_mus_interactive_ui_tests target

ui/views/mus/BUILD.gn

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/features.gni")
 import("//build/config/ui.gni")
 import("//mojo/public/mojo_application.gni")
 import("//mojo/public/mojo_application_manifest.gni")
 import("//testing/test.gni")
 import("//tools/grit/repack.gni")
@@ skipping 121 matching lines @@
 
   configs += [ "//build/config:precompiled_headers" ]
 
   # TODO(sky): add more files.
   sources = [
     "../run_all_unittests.cc",
     "../run_all_unittests.h",
     "../test/native_widget_factory_mus.cc",
     "../view_targeter_unittest.cc",
     "../widget/native_widget_unittest.cc",
+    "../widget/widget_interactive_uitest.cc",

[sky, 2016/05/13 19:27:52]

This needs to be in its own test harness. The reason for that is that these
tests have side effects. For example, they set system level capture. If you run
the tests here the tests will run in parallel, which can lead to flake.

     "../widget/widget_unittest.cc",
     "native_widget_mus_unittest.cc",
     "platform_test_helper_mus.cc",
     "platform_window_mus_unittest.cc",
     "run_all_unittests_mus.cc",
     "screen_mus_unittest.cc",
     "window_manager_connection_unittest.cc",
   ]
 
   deps = [
@@ skipping 80 matching lines @@
 }
 
 group("for_component") {
   public_deps = [
     ":mus",
   ]
   deps = [
     "//mojo/gles2",
   ]
 }