Iakiv Kramarenko

not sure if this is still open, need to check...

this feature needs some kine of "js selectors", let's think on allowing something like `browser.element('js:document.querySelector(".foo")')`, etc...

Example of project with configured Appium + Selene - https://github.com/qa-guru/mobile-tests-13-py

what about `have.texts('a', 'b', ...)` and `have.texts(..., 'd', 'e',)` instead of `have.first_texts('a', 'b')` and `have.last_texts('d', 'e')` correspondingly. What about even something like `have.texts(..., 'b', ...,'d',...)` ?

@SanKolts, you can definitely try to implement it on your side, by extending Element class or simply mankey patching the Selene's Element class. You can do it on your own...

Consider looking at this example of monkey patching Selene's Element class and others: https://github.com/qa-guru/mobile-tests-13-py/blob/main/mobile_tests_lesson_13/utils/selene/patch_element_mobile_commands.py https://github.com/qa-guru/mobile-tests-13-py/blob/main/mobile_tests_lesson_13/utils/selene/patch_selector_strategy.py https://github.com/qa-guru/mobile-tests-13-py/blob/main/conftest.py

> I'm not sure that I want to add it to my project as it is :) Why not? Looks like a fast and pretty nice solution:) until we find...

@SanKolts I liked your approach on «getting things done» in the last example of yours. Yet for Selene... I am not sure that this approach: > browser.element('.login-form').as_('auth_form').element('[label="Email"]').as_('email_field').click() should render a...

@SanKolts > If I use it without a path, my code is very redundant: > page.some_modal.some_modal_close_button.click() You code is rendundant not because of "selene might lack remembered path" but because...

reproduced something similar with "or_"... ``` cells = browser.all('selector') cells.should( have.text(f"{text_1} {text_2}") .or_(have.text(f"{text_2} {text_1}")) .or_(have.text(f"{text_2} {text_1}".upper())) ) ```  reported by ru selene user at https://t.me/selene_py_ru/7106