Delete all use of cricket::VideoFrame and cricket::WebRtcVideoFrame.

webrtc/media/base/testutils.h

Index: webrtc/media/base/testutils.h
diff --git a/webrtc/media/base/testutils.h b/webrtc/media/base/testutils.h
index 40034c0969a1709c1796dd41785544e288da1281..01a2a4f9c175d1a3456b36696242ad4779a040ea 100644
--- a/webrtc/media/base/testutils.h
+++ b/webrtc/media/base/testutils.h
@@ -29,6 +29,10 @@ class ByteBufferWriter;
 class StreamInterface;
 }
 
+namespace webrtc {
+class VideoFrame;

[perkj_webrtc, 2016/10/25 10:53:36]

why forward declare? style guide recommend include as much as possible.

[nisse-webrtc, 2016/10/25 11:21:01]

Really? Quoting
https://chromium.googlesource.com/chromium/src/+/master/styleguide/c++/c++.md :

"Unlike the Google style guide, Chromium style prefers forward declarations to
#includes where possible. This can reduce compile times and result in fewer
files needing recompilation when a header changes."

I don't have a strong opinion either way, but it's good to be consistent.

[perkj_webrtc, 2016/10/27 15:56:25]

interesting. I guess we follow chrome.

+}
+
 namespace cricket {
 
 // Returns size of 420 image with rounding on chroma for odd sizes.
@@ -115,7 +119,7 @@ class RtpTestUtility {
 // Test helper for testing VideoCapturer implementations.
 class VideoCapturerListener
     : public sigslot::has_slots<>,
-      public rtc::VideoSinkInterface<cricket::VideoFrame> {
+      public rtc::VideoSinkInterface<webrtc::VideoFrame> {
  public:
   explicit VideoCapturerListener(VideoCapturer* cap);
   ~VideoCapturerListener();
@@ -127,7 +131,7 @@ class VideoCapturerListener
   bool resolution_changed() const { return resolution_changed_; }
 
   void OnStateChange(VideoCapturer* capturer, CaptureState state);
-  void OnFrame(const VideoFrame& frame) override;
+  void OnFrame(const webrtc::VideoFrame& frame) override;
 
  private:
   VideoCapturer* capturer_;