PlzNavigate: Eliminate test_runner bailing out of layout tests too early

components/test_runner/web_frame_test_client.cc

Index: components/test_runner/web_frame_test_client.cc
diff --git a/components/test_runner/web_frame_test_client.cc b/components/test_runner/web_frame_test_client.cc
index d5eccbfef003146d05abff6b61fed71e42333fc5..2f40f36060d2a7cf13b7f201cc73e4cf727c6e7b 100644
--- a/components/test_runner/web_frame_test_client.cc
+++ b/components/test_runner/web_frame_test_client.cc
@@ -511,6 +511,18 @@ void WebFrameTestClient::didFinishLoad(blink::WebLocalFrame* frame) {
   }
 }
 
+void WebFrameTestClient::didNavigateWithinPage(
+    blink::WebLocalFrame* frame,
+    const blink::WebHistoryItem& history_item,
+    blink::WebHistoryCommitType commit_type,
+    bool contentInitiated) {
+  test_runner_->OnNavigationEnd();

[clamy, 2016/07/27 16:57:05]

Based on what we discussed offline, do you still need to call OnNavigationEnd if
we navigate in-page?

[blundell, 2016/07/29 15:02:46]

Yes, it's needed: there is at least one test where didStartLoading() is called
but neither didStartProvisionalLoadForFrame() nor didStopLoading() is ever
called. This patch needs the callback from didNavigateWithPage() to avoid that
test hanging. 

+}
+
+void WebFrameTestClient::didStartLoading(bool to_different_document) {
+  test_runner_->OnNavigationBegin();
+}
+
 void WebFrameTestClient::didStopLoading() {
   test_runner_->tryToClearTopLoadingFrame(
       web_frame_test_proxy_base_->web_frame());