Make custom EarlGrey matchers match Chromium style |
|||
Issue descriptionMost of the custom EarlGrey matchers are C-style methods, but start with a lowercase letter. This was done to match EarlGrey style, which is in violation. We should clean this up and make all of our custom matchers compliant with the Chromium style guide.
,
Jan 25 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/088977979f2bb20beb6215cbb09e8951b83a9b4c commit 088977979f2bb20beb6215cbb09e8951b83a9b4c Author: baxley <baxley@google.com> Date: Wed Jan 25 01:40:19 2017
,
Mar 23 2017
,
Mar 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1bc7717c1d7ccf5a90464a3fdf38536fd24d7fa8 commit 1bc7717c1d7ccf5a90464a3fdf38536fd24d7fa8 Author: baxley <baxley@chromium.org> Date: Fri Mar 24 01:03:40 2017 Fix style of custom matcher in settings_egtest.mm. EarlGrey matchers are C-Style methods and should start with a capital letter in Chromium. BUG= 680787 Review-Url: https://codereview.chromium.org/2777453002 Cr-Commit-Position: refs/heads/master@{#459315} [modify] https://crrev.com/1bc7717c1d7ccf5a90464a3fdf38536fd24d7fa8/ios/chrome/browser/ui/settings/settings_egtest.mm
,
Mar 28 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Jan 24 2017