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

Issue 2530873002: Expected stats list added to promise-based getStats WebRtcBrowserTest. (Closed)

Created:
4 years ago by hbos_chromium
Modified:
4 years ago
Reviewers:
hta - Chromium
CC:
chromium-reviews, feature-media-reviews_chromium.org, phoglund+watch_chromium.org, mcasas+watch+vc_chromium.org
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Expected stats list added to promise-based getStats WebRtcBrowserTest. Only allow expected/optional stats, fail if any expected stats are missing. Tests by RTCStats.type, not individual dictionary members. This helps ensure we have good coverage in the integration test and helps test against accidentally leaking an unexpected dictionary type. BUG=627816

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+57 lines, -16 lines) Patch
M chrome/browser/media/webrtc/webrtc_browsertest_base.cc View 1 chunk +1 line, -1 line 0 comments Download
M chrome/test/data/webrtc/peerconnection_getstats.js View 2 chunks +56 lines, -15 lines 1 comment Download

Messages

Total messages: 10 (6 generated)
hbos_chromium
Please take a look, hta. This is a simpler but less robust blink layer browser ...
4 years ago (2016-11-24 14:35:55 UTC) #4
hta - Chromium
lgtm I think this is a beautiful test, and tests exactly the right thing! Go ...
4 years ago (2016-11-24 15:45:00 UTC) #7
hbos_chromium
I landed https://codereview.chromium.org/2489673003/ in favor of this. They're modifying the same test. While both tests ...
4 years ago (2016-11-25 10:56:44 UTC) #8
hta - Chromium
4 years ago (2016-11-26 08:09:07 UTC) #10
Message was sent while issue was closed.
On 2016/11/25 10:56:44, hbos_chromium wrote:
> I landed https://codereview.chromium.org/2489673003/ in favor of this. They're
> modifying the same test. While both tests could be kept, the landed CL tests
the
> same thing this one does (and more), so having this becomes pointless.
> 
> The reason for this is I think having test coverage for dictionary members,
not
> just dictionary types, is worth the cost.

Looking at both, I agree. Please close this CL without landing.

Powered by Google App Engine
This is Rietveld 408576698