Add PeerConnectionInterface::UpdateCallBitrate.

webrtc/pc/peerconnectioninterface_unittest.cc

Index: webrtc/pc/peerconnectioninterface_unittest.cc
diff --git a/webrtc/pc/peerconnectioninterface_unittest.cc b/webrtc/pc/peerconnectioninterface_unittest.cc
index 05d53ad1a153fdcacc66f240d706c88f69d51f64..2a21f3ce8f69758c6d9c5eee75c8b37c6e9d06fd 100644
--- a/webrtc/pc/peerconnectioninterface_unittest.cc
+++ b/webrtc/pc/peerconnectioninterface_unittest.cc
@@ -3286,6 +3286,15 @@ TEST_F(PeerConnectionInterfaceTest,
   EXPECT_TRUE(DoSetLocalDescription(answer.release()));
 }
 
+TEST_F(PeerConnectionInterfaceTest, UpdateCallBitrateWithoutMinSucceeds) {
+  CreatePeerConnection();
+  PeerConnectionInterface::BitrateUpdate update;
+  update.start_bitrate_bps = rtc::Optional<int>(100000);
+  // Call doesn't expose its current config, so we just check that the
+  // call succeeds here.
+  pc_->UpdateCallBitrate(update);

[Taylor Brandstetter, 2017/04/07 03:29:12]

This test doesn't have any expectations, so is it mainly to verify that nothing
crashes? I'd mention that in a comment.

Can you also add a TODO to add a more meaningful test for this? I don't think
there's any easy way right now; the best we could do would probably be allowing
a "FakeCall" to be injected into PeerConnection (which we do in other places).

[Zach Stein, 2017/04/09 21:09:01]

The comment on 3293-3294 was my attempt to explain the lack of EXPECTs.

Should I just put the TODO after this test case?

[Taylor Brandstetter, 2017/04/10 04:59:51]

That would be fine.

+}
+
 class PeerConnectionMediaConfigTest : public testing::Test {
  protected:
   void SetUp() override {