Browser tests for OOPIF support for drag-n-drop.

content/test/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/chrome_build.gni")
 import("//build/config/compiler/compiler.gni")
 import("//build/config/crypto.gni")
 import("//build/config/features.gni")
 import("//build/config/ui.gni")
 import("//mojo/public/tools/bindings/mojom.gni")
@@ skipping 798 matching lines @@
   if (is_mac) {
     sources += [ "../renderer/external_popup_menu_browsertest.cc" ]
     deps += [ "//content/shell:content_shell" ]
     data += [ "$root_out_dir/Content Shell.app/" ]
   }
 
   if (is_chromeos) {
     deps += [ "//chromeos" ]
   }
 
+  if (use_aura) {
+    sources += [ "../browser/web_contents/drag_and_drop_browsertest.cc" ]

[Łukasz Anforowicz, 2016/11/01 23:43:42]

Hopefully aura-only only is okay for now.  aura-only means that we are ignoring
web_contents_view_android.cc and web_contents/web_drag_*_mac.mm

Also - for thinking about the proper level to do the drag-and-drop simulation,
it might be useful to note chrome/test/base/interactive_test_utils* which come
in multiple platform-specific flavors.  For now the new browser test can live in
the //content layer though, so landing the CL as-is seems okay.

+  }
+
   if (use_aura && !is_win) {
     deps += [ "//ui/events:test_support" ]
   }
 
   if (!use_aura && !is_mac) {
     sources -=
         [ "../browser/compositor/image_transport_factory_browsertest.cc" ]
   }
 
   if (enable_webrtc) {
@@ skipping 864 matching lines @@
   if (is_android) {
     deps += [ "//testing/android/native_test:native_test_native_code" ]
   }
 }
 
 group("fuzzers") {
   deps = [
     "//content/test/fuzzer",
   ]
 }