widgetastic.core
widgetastic.core copied to clipboard
RedHatQE
Making testing of UIs fantastic.
In the old framework we had the ability to fill a Select/Downdown by Value as well as by Text. In WT we can currently only fill by Text. The consequence...
Basically, up until now widgetastic executed the ensure_page_safe before EVERY element lookup. Now it does it only if it hits an error. Also added some post-action ensure_page_safe calls. That should...
We should able to access other instances of ParametrizedView. More info for this need could be found in this PR: https://github.com/ManageIQ/integration_tests/pull/4769
I was thinking about this before, widgetastic is currently very pedantic with page checking so it is relatively slow. There is a possibility to keep these check obligatory only after...
We already have parametrized views but a parametrized Widget would also be nice. Current code sample: ```python def _remove_recipient(self, email): Text(self, ".//a[text()='{}']".format(email)).click() ``` What I would imagine: ```python class Foo(View):...
Currently, we have is_displayed that only returns true or false without further explanation. It would be helpful to see which exact part of the is_displayed failed. Therefore I would propose...