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

Issue 1578133002: Make all site engagement tests run on Android. (Closed)

Created:
4 years, 11 months ago by dominickn
Modified:
4 years, 11 months ago
Reviewers:
calamity, benwells
CC:
chromium-reviews, chrome-apps-syd-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Make all site engagement tests run on Android. The current site engagement tests are a) based on BrowserWithTestWindowTest (which doesn't run on Android); or b) not compiled as part of unit_tests on Android. This CL refactors the tests so that they compile, run, and pass on Android. BUG=575509 Committed: https://crrev.com/330431253754734118f7f1dc842af1f81c6c485c Cr-Commit-Position: refs/heads/master@{#369364}

Patch Set 1 #

Total comments: 4

Patch Set 2 : Addressing nit #

Unified diffs Side-by-side diffs Delta from patch set Stats (+86 lines, -106 lines) Patch
M chrome/browser/engagement/site_engagement_helper.cc View 1 chunk +0 lines, -1 line 0 comments Download
M chrome/browser/engagement/site_engagement_helper_unittest.cc View 19 chunks +56 lines, -75 lines 0 comments Download
M chrome/browser/engagement/site_engagement_service_unittest.cc View 1 5 chunks +27 lines, -27 lines 0 comments Download
M chrome/chrome_tests_unit.gypi View 1 2 chunks +3 lines, -3 lines 0 comments Download

Messages

Total messages: 11 (3 generated)
dominickn
PTAL, thanks!
4 years, 11 months ago (2016-01-12 06:13:21 UTC) #2
benwells
https://codereview.chromium.org/1578133002/diff/1/chrome/browser/engagement/site_engagement_service_unittest.cc File chrome/browser/engagement/site_engagement_service_unittest.cc (left): https://codereview.chromium.org/1578133002/diff/1/chrome/browser/engagement/site_engagement_service_unittest.cc#oldcode379 chrome/browser/engagement/site_engagement_service_unittest.cc:379: base::CommandLine::ForCurrentProcess()->AppendSwitch( How come the flag isn't needed? https://codereview.chromium.org/1578133002/diff/1/chrome/browser/engagement/site_engagement_service_unittest.cc File ...
4 years, 11 months ago (2016-01-13 23:14:32 UTC) #3
dominickn
https://codereview.chromium.org/1578133002/diff/1/chrome/browser/engagement/site_engagement_service_unittest.cc File chrome/browser/engagement/site_engagement_service_unittest.cc (left): https://codereview.chromium.org/1578133002/diff/1/chrome/browser/engagement/site_engagement_service_unittest.cc#oldcode379 chrome/browser/engagement/site_engagement_service_unittest.cc:379: base::CommandLine::ForCurrentProcess()->AppendSwitch( On 2016/01/13 23:14:32, benwells wrote: > How come ...
4 years, 11 months ago (2016-01-14 01:17:41 UTC) #4
benwells
lgtm
4 years, 11 months ago (2016-01-14 01:58:49 UTC) #5
calamity
lgtm
4 years, 11 months ago (2016-01-14 06:34:22 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1578133002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1578133002/20001
4 years, 11 months ago (2016-01-14 06:45:59 UTC) #8
commit-bot: I haz the power
Committed patchset #2 (id:20001)
4 years, 11 months ago (2016-01-14 07:41:50 UTC) #9
commit-bot: I haz the power
4 years, 11 months ago (2016-01-14 07:44:30 UTC) #11
Message was sent while issue was closed.
Patchset 2 (id:??) landed as
https://crrev.com/330431253754734118f7f1dc842af1f81c6c485c
Cr-Commit-Position: refs/heads/master@{#369364}

Powered by Google App Engine
This is Rietveld 408576698