Related: https://playwright.dev/ has a built-in code generator. In *my opinion*, it's also more pleasant to work with than Selenium.
[deleted]
Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
11–20 of 131 posts
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#12I don't get why people still use XPaths, CSS selectors or HTML IDs to identify elements, even when they are "recorded". Please please please just use my https://github.com/mherrmann/selenium-python-helium instead. It makes so much more sense.
[deleted]
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#13Curious which part of this uses AI. Doesnt it just track mouse / keyboard events across the session?
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#14I don't get why people still use XPaths, CSS selectors or HTML IDs to identify elements, even when they are "recorded". Please please please just use my https://github.com/mherrmann/selenium-python-helium instead. It makes so much more sense.
Why wouldn't you use CSS selectors? They are unambiguous, concise and most importantly, a standard. They should be the conventional way to refer to elements.
The CSS structure of a web site is an implementation detail and on a global average, CSS selectors break much more often than user-visible labels.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#15Curious which part of this uses AI. Doesnt it just track mouse / keyboard events across the session?
AI looks to be involved in creating element selectors.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#16Related: https://playwright.dev/ has a built-in code generator. In *my opinion*, it's also more pleasant to work with than Selenium.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#17I don't get why people still use XPaths, CSS selectors or HTML IDs to identify elements, even when they are "recorded". Please please please just use my https://github.com/mherrmann/selenium-python-helium instead. It makes so much more sense.
This is the idea behind Testing-Library from what I understand.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#18I don't get why people still use XPaths, CSS selectors or HTML IDs to identify elements, even when they are "recorded". Please please please just use my https://github.com/mherrmann/selenium-python-helium instead. It makes so much more sense.
Why wouldn't you use CSS selectors? They are unambiguous, concise and most importantly, a standard. They should be the conventional way to refer to elements.
> and most importantly, a standard.
A standard for what, exactly? Selecting HTML elements? You could say the same about XPath.
Both are implementation details tightly coupled to the code instead of being driven by the “human” elements of the UI, such as the visible text, labels, etc.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#19I don't get why people still use XPaths, CSS selectors or HTML IDs to identify elements, even when they are "recorded". Please please please just use my https://github.com/mherrmann/selenium-python-helium instead. It makes so much more sense.
I haven't found anything that made me really need to try other things, but the fact that it's just a wrapper and sounds like it handles nested iframes better means I'm trying this next time I need to make a quick selenium script. Thank you
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#20What distinguishes this from UI.Vision's (https://ui.vision/) session recorder?