Simplify VideoEncoder interface.

remoting/codec/video_encoder_verbatim_unittest.cc

Index: remoting/codec/video_encoder_verbatim_unittest.cc
diff --git a/remoting/codec/video_encoder_verbatim_unittest.cc b/remoting/codec/video_encoder_verbatim_unittest.cc
index d6315ee3ccae2d1e9a537186c0382933981d2ec8..aa3f17e2e4e848f0d0b0cb110a917ab6d97b5135 100644
--- a/remoting/codec/video_encoder_verbatim_unittest.cc
+++ b/remoting/codec/video_encoder_verbatim_unittest.cc
@@ -12,13 +12,7 @@ namespace remoting {
 
 TEST(VideoEncoderVerbatimTest, TestVideoEncoder) {
   scoped_ptr<VideoEncoderVerbatim> encoder(new VideoEncoderVerbatim());
-  TestVideoEncoder(encoder.get(), true);
-}
-
-TEST(VideoEncoderVerbatimTest, TestVideoEncoderSmallOutputBuffer) {
-  scoped_ptr<VideoEncoderVerbatim> encoder(new VideoEncoderVerbatim());
-  encoder->SetMaxPacketSize(16);
-  TestVideoEncoder(encoder.get(), true);
+  TestVideoEncoder(encoder.get(), false);

[Wez, 2013/09/12 14:20:15]

Why not strict?

[Sergey Ulanov, 2013/09/12 19:18:45]

strict makes the test verify that the rect specified in VideoPacketFormat
matches expected. Only the old verbatim codec used these fields. They are not
used anymore, so it doesn't make sense to check them. 

Basically the test was written with the assumption that we send one rect per
packet instead of one frame per packet. That doesn't make sense with either of
the codecs now.

Removed these fields from protobufs, cleaned up the test and changed this back
to true.

 }
 
 TEST(VideoEncoderVerbatimTest, EncodeAndDecode) {
@@ -27,11 +21,4 @@ TEST(VideoEncoderVerbatimTest, EncodeAndDecode) {
   TestVideoEncoderDecoder(encoder.get(), decoder.get(), false);
 }
 
-TEST(VideoEncoderVerbatimTest, EncodeAndDecodeSmallOutputBuffer) {
-  scoped_ptr<VideoEncoderVerbatim> encoder(new VideoEncoderVerbatim());
-  encoder->SetMaxPacketSize(16);
-  scoped_ptr<VideoDecoderVerbatim> decoder(new VideoDecoderVerbatim());
-  TestVideoEncoderDecoder(encoder.get(), decoder.get(), false);
-}
-
 }  // namespace remoting