Fix some unit_tests under PlzNavigate

content/public/test/test_renderer_host.cc

Index: content/public/test/test_renderer_host.cc
diff --git a/content/public/test/test_renderer_host.cc b/content/public/test/test_renderer_host.cc
index d385871bbf9ea30a84975834abc2050cec70f82a..8765eef5cc25f117f53e8df564e92452e7402873 100644
--- a/content/public/test/test_renderer_host.cc
+++ b/content/public/test/test_renderer_host.cc
@@ -16,9 +16,9 @@
 #include "content/public/browser/browser_thread.h"
 #include "content/public/browser/web_contents.h"
 #include "content/public/common/browser_side_navigation_policy.h"
+#include "content/public/test/browser_side_navigation_test_utils.h"
 #include "content/public/test/mock_render_process_host.h"
 #include "content/public/test/test_browser_context.h"
-#include "content/test/browser_side_navigation_test_utils.h"
 #include "content/test/content_browser_sanity_checker.h"
 #include "content/test/test_render_frame_host.h"
 #include "content/test/test_render_frame_host_factory.h"
@@ -60,6 +60,10 @@ RenderFrameHost* RenderFrameHostTester::GetPendingForController(
     NavigationController* controller) {
   WebContentsImpl* web_contents = static_cast<WebContentsImpl*>(
       controller->GetWebContents());
+  if (IsBrowserSideNavigationEnabled()) {
+    return web_contents->GetRenderManagerForTesting()

[clamy, 2016/08/30 21:17:47]

Which test need to get access to the pending RFH?

@nasko: for a long time we did not want to expose the speculative RFH outside of
content, since it is an implementation detail that may go away. Are we okay to
do so now?

[scottmg, 2016/08/30 21:55:27]

That was for ToolbarModelTest (and maybe others), via
https://cs.chromium.org/chromium/src/chrome/test/base/browser_with_test_windo...
otherwise the wrong url was active here
https://cs.chromium.org/chromium/src/chrome/browser/ui/toolbar/toolbar_model_...
. I don't full understand the details, so let me know if that doesn't seem to
make much sense and I'll dig in more.

[clamy, 2016/08/30 23:08:38]

As explained in the new patchset, I think we can actually use
WebContentsTester::CommitPendingNavigation in BrowserWithTestWindowTest, which
should remove the need for accessing the pending RFH in that function.

+        ->speculative_render_frame_host_.get();
+  }
   return web_contents->GetRenderManagerForTesting()->pending_frame_host();
 }