Use ScopedTaskEnvironment instead of MessageLoop in tests that use v8.

content/public/test/render_view_test.cc

 // Copyright (c) 2012 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.
 
 #include "content/public/test/render_view_test.h"
 
 #include <stddef.h>
 
 #include <cctype>
 
@@ skipping 138 matching lines @@
 }
 
 RenderViewTest::RenderViewTest()
     : view_(NULL) {
   RenderFrameImpl::InstallCreateHook(&TestRenderFrame::CreateTestRenderFrame);
 }
 
 RenderViewTest::~RenderViewTest() {
 }
 
 void RenderViewTest::ProcessPendingMessages() {

[sky, 2017/05/04 02:58:55]

How about removing this function entirely and having callers use
base::RunLoop().RunUntilIdle() directly?

[fdoray, 2017/05/08 15:22:08]

Done in a separate CL https://codereview.chromium.org/2870633002/

-  msg_loop_.task_runner()->PostTask(FROM_HERE,
-                                    base::MessageLoop::QuitWhenIdleClosure());
-  base::RunLoop().Run();
+  base::RunLoop().RunUntilIdle();
 }
 
 WebLocalFrame* RenderViewTest::GetMainFrame() {
   return view_->GetWebView()->MainFrame()->ToWebLocalFrame();
 }
 
 void RenderViewTest::ExecuteJavaScriptForTests(const char* js) {
   GetMainFrame()->ExecuteScript(WebScriptSource(WebString::FromUTF8(js)));
 }
 
@@ skipping 495 matching lines @@
       static_cast<TestRenderFrame*>(impl->GetMainRenderFrame());
   frame->Navigate(common_params, StartNavigationParams(), request_params);
 
   // The load actually happens asynchronously, so we pump messages to process
   // the pending continuation.
   FrameLoadWaiter(frame).Wait();
   view_->GetWebView()->UpdateAllLifecyclePhases();
 }
 
 }  // namespace content