I recently wrote a blog post where I take a deep look into Playwright’s locators, specifically comparing the Page#getByRole locator with CSS selectors in terms of performance.
Playwright’s getByRole is 1.5x slower than CSS selectors because Page#getByRole uses querySelectorAll('*') and matches elements by the accessible name.
The post breaks down how `getByRole` works under the hood, how it stacks up against CSS selectors performance-wise, and what this means for your testing suites.
SerpApi | https://serpapi.com | Senior Ruby Engineer | Creative Director | Based in Austin, TX but everyone is remote | Full-time | ONSITE or FULLY REMOTE (We're a remote first company) | $160k 1099 for US or local avg + 20% for outside the US
SerpApi is the leading API to scrape and parse search engine results. We deeply support Google, Google Maps, Google Images, Bing, Baidu, and a lot more.
Our current stack is Ruby, Rails, MongoDB, and React.JS. We are looking for a Creative Director and a Senior Engineer. For the Creative Director position, we're looking for someone to give us a strong visual direction and experience in CSS, JS, or React are definitely plusses but not required.
We have an awesome work environment: We are a remote first company (before Covid!). We do continuous integration, continuous deployments, code reviews, code pairings, profit sharing, and most of communication is async via GitHub.
We value super strongly transparency, do open books, have a public roadmap, and contribute to the EFF.
> The google search function is also limited. For comparison, SerpAPI masterfully scrapes Google Search using a proxy network and very intelligent parsing. In experiments using SerpAPI in combination with Microsoft’s guidance module, I got much farther than AutoGPT.
This is a very interesting point of view. Can you describe it more in detail or share links to read about the topic "orthogonal cartesian view of the world vs others"?
I was debugging the Bing Image Search. Ctrl+Shift+F in the browser dev tools din't work to find the request by contents. I've used mitmproxy and then found a up-to-date way to filter responses by string in contents in the devtools.
This post contains steps to understand "where the data is coming from in the web app". Please share your feedback.
Essentially, the prompt was `apply TDD or Nielsen's user testing to agents-observing-agents via tmux or subprocesses`.
Details are on the blog post and GitHub repo.