Run ContentMain in a browser_test's browser process. This removes duplication of code in the browse…

ash/drag_drop/drag_drop_interactive_uitest.cc

Index: ash/drag_drop/drag_drop_interactive_uitest.cc
===================================================================
--- ash/drag_drop/drag_drop_interactive_uitest.cc	(revision 257128)
+++ ash/drag_drop/drag_drop_interactive_uitest.cc	(working copy)
@@ -12,6 +12,7 @@
 #include "ui/aura/window_event_dispatcher.h"
 #include "ui/base/dragdrop/drag_drop_types.h"
 #include "ui/base/test/ui_controls.h"
+#include "ui/gl/gl_surface.h"
 #include "ui/views/view.h"
 #include "ui/views/widget/widget.h"
 
@@ -118,8 +119,17 @@
 
 }  // namespace
 
-typedef test::AshTestBase DragDropTest;
+class DragDropTest : public test::AshTestBase {
+ public:
+  DragDropTest() {}
+  virtual ~DragDropTest() {}
 
+  virtual void SetUp() OVERRIDE {
+    gfx::GLSurface::InitializeOneOffForTests();

[sky, 2014/03/14 21:35:56]

Is there a reason you don't want to move this to AshTestBase?

[jam, 2014/03/14 22:35:40]

yeah, it won't work because this test base class runs in both unit test and
browser test binaries. In the former, the environment already calls this method.
if i put it in the base, it would be called twice which fails.

+    test::AshTestBase::SetUp();
+  }
+};
+
 #if defined(OS_WIN)
 #define MAYBE_DragDropAcrossMultiDisplay DISABLED_DragDropAcrossMultiDisplay
 #else