WaitForTimeInterval action is not working in XCUIT Franky |
|||
Issue descriptionApp Version: 63.0.3231.0 canary iOS Version: 10.3.3 Device: iPhone 7 Steps to reproduce: 1. Launch Chrome 2. Run the test case having a wait action Note 1 : For reference please consider P1 test case: “First Run Sign-in (with ASP account) with Passphrase” Note 2: Appium Version: 1.6.4, Xcode version: 8.3.3, selenium version: 3.3.1 and XCUIT version: 2.27.2 Observed Results: Instead of waiting for the given time it simply moves to the next step Expected results: The test run should hold as per the given wait time.
,
Oct 23 2017
,
Mar 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src/tools/franky/+/618a75f13a6036cfaf6b851851c1c6b955498b82 commit 618a75f13a6036cfaf6b851851c1c6b955498b82 Author: Lindsay Pasricha <lindsayw@google.com> Date: Thu Mar 08 21:00:12 2018 Fix ClearBrowsingData and implicitlyWait Add a sleep for clearBrowsingData and a workaround for implicitlyWait Bug: 777344 Change-Id: I58968ff78d18a84cd78b0debc78529f1fa48f6ea Reviewed-on: https://chromium-review.googlesource.com/943941 Reviewed-by: Benjamin Joyce <bjoyce@google.com> Reviewed-by: Sergey Berezin <sergeyberezin@chromium.org> [modify] https://crrev.com/618a75f13a6036cfaf6b851851c1c6b955498b82/franky/actions/timeout.py [modify] https://crrev.com/618a75f13a6036cfaf6b851851c1c6b955498b82/franky/actions/settings.py
,
Mar 12 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by baxley@chromium.org
, Oct 23 2017