Re-enable scenarioToTestAccessibilityOnChromium |
|||
Issue descriptionTest is consistently failing on phones with iOS10. Failure example: https://uberchromegw.corp.google.com/i/internal.bling.main/builders/iphone10-device-x64/builds/731/steps/chrome_kif_integration_tests%20%28iPhone%206s%20iOS%2010.0.1%29%20on%20iOS-10.0.1 The log, for posterity: https://paste.googleplex.com/4579767802134528
,
Oct 20 2016
+baxley This is a KIF test. Does it need to be maintained?
,
Oct 20 2016
Regarding a11y tests, we can add Lindsay to it. However, this case looks to be something failing consistently on device, so we're looking into it. To answer the questions, we shouldn't be doing much work on KIF tests, most aren't needed. But failures should still be investigated, in case it's a Chrome problem.
,
Oct 20 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 commit 3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 Author: jif <jif@google.com> Date: Thu Oct 20 18:54:59 2016
,
Oct 20 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 commit 3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 Author: jif <jif@google.com> Date: Thu Oct 20 18:54:59 2016
,
Oct 20 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 commit 3737a68dc59dd68a5dcf5ecbebd00dd2af4c0627 Author: jif <jif@google.com> Date: Thu Oct 20 18:54:59 2016
,
Oct 20 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/062b5908a9bf2527192d9c5b64787d35fadeeba7 commit 062b5908a9bf2527192d9c5b64787d35fadeeba7 Author: jif <jif@google.com> Date: Thu Oct 20 19:18:45 2016 |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Oct 20 2016