Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(27)

Unified Diff: webrtc/modules/pacing/alr_detector_unittest.cc

Issue 2970653004: Reimplemeted "Test and fix for huge bwe drop after alr state" (Closed)
Patch Set: Respond to comments Created 3 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: webrtc/modules/pacing/alr_detector_unittest.cc
diff --git a/webrtc/modules/pacing/alr_detector_unittest.cc b/webrtc/modules/pacing/alr_detector_unittest.cc
index e1a78103dfa235b8333b1529af6fbe59267b43b9..9f1998b617bb753a6aba57c99b26eb33c51f9786 100644
--- a/webrtc/modules/pacing/alr_detector_unittest.cc
+++ b/webrtc/modules/pacing/alr_detector_unittest.cc
@@ -86,7 +86,7 @@ TEST_F(AlrDetectorTest, AlrDetection) {
// Verify that we ALR starts when bitrate drops below 20%.
SimulateOutgoingTrafficIn(&alr_detector_)
- .ForTimeMs(1000)
+ .ForTimeMs(1500)
.AtPercentOfEstimatedBitrate(20);
EXPECT_TRUE(alr_detector_.GetApplicationLimitedRegionStartTime());
@@ -109,7 +109,7 @@ TEST_F(AlrDetectorTest, ShortSpike) {
// Verify that we stay in ALR region even after a short bitrate spike.
SimulateOutgoingTrafficIn(&alr_detector_)
- .ForTimeMs(200)
+ .ForTimeMs(100)
.AtPercentOfEstimatedBitrate(150);
EXPECT_TRUE(alr_detector_.GetApplicationLimitedRegionStartTime());
« no previous file with comments | « webrtc/modules/pacing/alr_detector.h ('k') | webrtc/modules/remote_bitrate_estimator/test/estimators/send_side.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698