Account for different element visibility states in tests.
The Captured Sites Automation Framework interacts with real-life pages. By default, the framework expects that a page element to be visible, enabled and on top of the page. In the Chrome Autofill tests, some sites break this expection. Some address or credit card fields are hidden inputs, and some customized combo boxes have a selection element hide behind sibling span elements. Today, the test framework fails when encountering these exceptions. The Action Recorder Extension already logs the visibility state of each element it records. This change takes account of the element visibility state information inside the recipe files. Bug: 847905 Change-Id: Ibed7beef309d1bfbfb285cae02d026e172da8fb4 Reviewed-on: https://chromium-review.googlesource.com/c/1332701Reviewed-by:Sebastien Seguin-Gagnon <sebsg@chromium.org> Commit-Queue: Yiming Zhou <uwyiming@google.com> Cr-Commit-Position: refs/heads/master@{#607433}
Showing
Please register or sign in to comment