Fixed quality tests after PyAuto test purge.

chrome/test/data/webrtc/video_extraction.js

Index: chrome/test/data/webrtc/video_extraction.js
diff --git a/chrome/test/data/webrtc/video_extraction.js b/chrome/test/data/webrtc/video_extraction.js
index bf01dc46581407bfe85d8fba467287ec03642296..93cf9e7fc49312342d6aab5981f2dd9bf666a273 100644
--- a/chrome/test/data/webrtc/video_extraction.js
+++ b/chrome/test/data/webrtc/video_extraction.js
@@ -190,6 +190,7 @@ function sendFrames() {
   if (!gWebSocketOpened) {
     console.log('WebSocket connection is not yet open');
     setTimeout(function() { sendFrames(); }, 100);
+    return;

[kjellander_chromium, 2014/04/07 14:59:58]

Just curious, why is this needed?

[phoglund_chromium, 2014/04/08 09:29:00]

The point of this code is "if the websocket is not open, call sendFrames 100 ms
later and hope it is open then". That's not what it does though; it schedules
sendFrames in 100 ms and proceeds to execute the code that is dependent on the
websocket being open. So the send on line 199 is just going to fail. This
doesn't make any sense which is why I added the return. This bug has probably
been here since the websocket has never failed to get up earlier.

   }
 
   progressBar = document.getElementById('progress-bar');