Keyword driven automation for the web
APACHE-2.0 License
Bot releases are hidden (Show)
<slot>
Published by tkoukkari 7 months ago
Published by tkoukkari 9 months ago
Published by tkoukkari 10 months ago
Published by tkoukkari 12 months ago
SetConfig HandleAlerts False
was not raising exceptionsSetConfig RunBefore
Published by tkoukkari about 1 year ago
Minor bug fix release.
Published by tkoukkari about 1 year ago
Published by tkoukkari about 1 year ago
Minor bugfix release.
Published by tkoukkari over 1 year ago
Published by tkoukkari over 1 year ago
Published by tkoukkari over 1 year ago
Published by tkoukkari over 1 year ago
# Mobile emulation
OpenBrowser http://google.com chrome emulation=iPhone SE
OpenBrowser http://google.com chrome emulation=375x812
Published by tkoukkari almost 2 years ago
Published by tkoukkari almost 2 years ago
pip install -U QWeb
Published by tkoukkari almost 2 years ago
Minor bug fix release
Published by tkoukkari about 2 years ago
Published by tkoukkari about 2 years ago
Published by tkoukkari over 2 years ago
Published by tkoukkari over 2 years ago
Published by tkoukkari over 2 years ago
Changes:
Enhanced Shadow DOM support
There has been more and more cases where some (or all) elements are under shadow dom. These have been reachable via javascript only. However, it usually results hard-to-maintain test scripts like this:
GoTo chrome://settings/content/popups
${enable_popups_btn}= Set Variable document.querySelector("settings-ui").shadowRoot.querySelector("settings-main").shadowRoot.querySelector("settings-basic-page").shadowRoot.querySelector("div#basicPage").querySelector("[page-title='Privacy and security'] > settings-privacy-page").shadowRoot.querySelector("settings-animated-pages > settings-subpage > settings-category-default-radio-group").shadowRoot.querySelector("[id=radioSection] > settings-radio-group > settings-collapse-radio-button").shadowRoot.querySelector("[id=radioCollapse] > [id=button]")
ExecuteJavascript ${enable_popups_btn}.click()
...which are prone to break if the DOM structure changes at all.
We have now added enhanced Shadow DOM support for all keywords that handle textual locators (*Text), inputs (*Input) or attribute value locators (*Item). At least for now we have this under a feature flag/setting, because old test cases might potentially suddenly find more elements than before.
As an example, the above test case can be re-written in a more clear way using the new feature:
SetConfig ShadowDOM True # extends search to shadow dom elements
GoTo chrome://settings/content/popups
ClickText Sites can send pop-ups
More examples can be found for example in our tests here:
https://github.com/qentinelqi/qweb/blob/master/test/acceptance/shadow_dom.robot
Highlight color
There have been few cases where it would be useful to easily identify which of the duplicated elements QWeb finds. You can do this by changing the highlight color.
Example:
VerifyItem text anchor=2 # highlight element using default color (blue)
SetConfig HighlightColor orange
VerifyItem text anchor=Local Target in Shadow DOM