|
|
Chromium Code Reviews
Descriptionmedia: Add Permissions.Action.ProtectedMedia UMA on ChromeOS
BUG=719111
TEST=Maually tested
Review-Url: https://codereview.chromium.org/2864113002
Cr-Commit-Position: refs/heads/master@{#470160}
Committed: https://chromium.googlesource.com/chromium/src/+/caeedfbcb7eb8a9a9a1a262c385af7c49045a864
Patch Set 1 #
Messages
Total messages: 27 (13 generated)
xhwang@chromium.org changed reviewers: + ddorwin@chromium.org, jrummell@chromium.org
xhwang@chromium.org changed required reviewers: + jrummell@chromium.org
jrummell: PTAL ddorwin: FYI
The CQ bit was checked by xhwang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Don't you need to update histograms.xml with the new entry? Otherwise lgtm.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
xhwang@chromium.org changed reviewers: + isherman@chromium.org
isherman: FYI, this CL enables UMA reporting of an existing UMA on ChromeOS. Previously we only have data reported on Android. This is why I don't need to update histograms.xml.
raymes@chromium.org changed reviewers: + raymes@chromium.org
Thanks for adding this. Should we add a test for this?
On 2017/05/07 22:13:47, raymes wrote: > Thanks for adding this. Should we add a test for this? Good question. How do we add tests for UMAs? Also this would require user actions. Do you have any examples?
Metrics LGTM, thanks. The HistogramTester class would probably be useful for adding test coverage.
On 2017/05/08 17:52:17, xhwang wrote: > On 2017/05/07 22:13:47, raymes wrote: > > Thanks for adding this. Should we add a test for this? > > Good question. How do we add tests for UMAs? Also this would require user > actions. Do you have any examples? raymes@: It seems there's no unittest for PlatformVerificationDialog either, probably for the same reason: needs user action. So I don't see any easy way of adding tests. We have a plan to switch to use standard permission bubble for this: https://bugs.chromium.org/p/chromium/issues/detail?id=454847, after which it'll be easier to add tests I guess.
On 2017/05/08 17:52:17, xhwang wrote: > On 2017/05/07 22:13:47, raymes wrote: > > Thanks for adding this. Should we add a test for this? > > Good question. How do we add tests for UMAs? Also this would require user > actions. Do you have any examples? raymes@: It seems there's no unittest for PlatformVerificationDialog either, probably for the same reason: needs user action. So I don't see any easy way of adding tests. We have a plan to switch to use standard permission bubble for this: https://bugs.chromium.org/p/chromium/issues/detail?id=454847, after which it'll be easier to add tests I guess.
On 2017/05/08 18:24:15, xhwang wrote: > On 2017/05/08 17:52:17, xhwang wrote: > > On 2017/05/07 22:13:47, raymes wrote: > > > Thanks for adding this. Should we add a test for this? > > > > Good question. How do we add tests for UMAs? Also this would require user > > actions. Do you have any examples? > > raymes@: It seems there's no unittest for PlatformVerificationDialog either, > probably for the same reason: needs user action. So I don't see any easy way of > adding tests. We have a plan to switch to use standard permission bubble for > this: https://bugs.chromium.org/p/chromium/issues/detail?id=454847, after which > it'll be easier to add tests I guess. Ok - I don't know that code so well so I will leave it up to you :)
On 2017/05/08 21:40:00, raymes wrote: > On 2017/05/08 18:24:15, xhwang wrote: > > On 2017/05/08 17:52:17, xhwang wrote: > > > On 2017/05/07 22:13:47, raymes wrote: > > > > Thanks for adding this. Should we add a test for this? > > > > > > Good question. How do we add tests for UMAs? Also this would require user > > > actions. Do you have any examples? > > > > raymes@: It seems there's no unittest for PlatformVerificationDialog either, > > probably for the same reason: needs user action. So I don't see any easy way > of > > adding tests. We have a plan to switch to use standard permission bubble for > > this: https://bugs.chromium.org/p/chromium/issues/detail?id=454847, after > which > > it'll be easier to add tests I guess. > > Ok - I don't know that code so well so I will leave it up to you :) Okay, thanks for the comments!
The CQ bit was checked by xhwang@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by xhwang@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 1, "attempt_start_ts": 1494287308580690, "parent_rev":
"3d83dad2db679c3924ffe74599cfd48a03211778", "commit_rev":
"caeedfbcb7eb8a9a9a1a262c385af7c49045a864"}
Message was sent while issue was closed.
Description was changed from ========== media: Add Permissions.Action.ProtectedMedia UMA on ChromeOS BUG=719111 TEST=Maually tested ========== to ========== media: Add Permissions.Action.ProtectedMedia UMA on ChromeOS BUG=719111 TEST=Maually tested Review-Url: https://codereview.chromium.org/2864113002 Cr-Commit-Position: refs/heads/master@{#470160} Committed: https://chromium.googlesource.com/chromium/src/+/caeedfbcb7eb8a9a9a1a262c385a... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/caeedfbcb7eb8a9a9a1a262c385a... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
