Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
81–90 of 131 posts
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#82> This will launch a Chrome session controlled by Selenium and then log you in to Google Why is logging into Google a requirement?
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#83Earlier quoted context omitted.
Good to know! The comments have definitely made us update towards looking into Playwright again quite seriously
Yeah - I moved my entire automation library over at the beginning of the year. The docker integrations and ease of switching out browsers without having to manage webdrivers individually sealed the deal. I'm also tentatively using their selectors a bit, although find I have to retreat to Xpath quite a bit. Playwright seems to be the obvious choice for testing - but automation who knows. If you can be playwright for a…
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#84Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#85I'm working on something kind of similar but for Appium. This is excellent work!
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#86Could this work for other languages, for example, R?
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#87I am building _exactly_ the same thing for Playwright over at https://ray.run/ . I think this is the future of writing tests no doubt. Planning to launch next week. By the looks of it, I am taking a slightly different approach than you. I am using LLM only to identify elements, but the actual generators are created using https://ray.run/browser-extension
Edit: or just disabled in general cos it's super annoying
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#88Earlier quoted context omitted.
Interesting, what features are most impactful in making it more pleasant to work with? We picked Selenium because it seems much more widely used at least in the Python world (selenium has about 10x more downloads on PyPI than playwright). My guess is that's at least partly because Playwright is more focused on the JS/TS ecosystem and testing.
Wildly better developer experience. Playwright is also much less flakey and easier to work with than cypress, another alternative to selenium. Selenium is quite outdated, though still widely used. It's much older. I would look at downloads over time / rate of change, not total downloads. My hot take- don't hook yourselves to outdated tech. Don't take my word for it- go try out selenium, Cypress, and playwright and dr…
https://github.com/w3c/webdriver-bidi
https://w3c.github.io/webdriver-bidi/
Google wrote a good explainer about WebDriver BiDi here:
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#89This is amazing. I will try to have it automate my system of agents web app in a meaningful way (turtles all the way down.) Shameless plug: https://github.com/agi-merge/waggle-dance BTW I don’t normally use Chrome- I know why you would start with that, but it would be great to see a Firefox or even Safari version of this.
Re: Show HN: Autotab – An AI-powered Chrome extension to create Selenium scripts
#90:)