446: All about rewrites

This episode is brought to you by WorkOS. If you're building a b two b ass app, at some point, your customers will start asking for enterprise features like single sign on, skim, provisioning, role based access control, and audit trails. That's where WorkOS comes in. With ease to use and flexible APIs that help you ship enterprise features on day one without slowing down your core product development. Today, some of the hottest startups in the world are already powered by WorkOS, including ones you probably know, like Perplexity, Vercel, Jasper, and Webflow. WorkOS also provides a generous free tier of up to 1,000,000 monthly active users for its user management solution, making it the perfect authentication and authorization solution for growing companies. It comes standard with rich features like social logins, bot protection, MFA, roles and permissions and more. If you're currently looking to build SSO for your first enterprise customer, you should consider using WorkOS. Integrate in minutes and start shipping enterprise plans today. Check it all out at workos.com. That's workos.com. Hello, and welcome to another episode of The Bike Shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Stephanie Eeman. And I'm Joel Kenville. And together, we're here to share a bit of what we've learned along the way. So, Joel, what's new in your world? I recently read an article on configuring capybara, sort of a test UI library that a lot of Rails apps use to interact with end to end tests. And there's a bunch of things that you can configure on it that I didn't realize that will allow its selectors to just pick up things by name. So by default, you can target any form input by the name of its label or its ID or its name attribute. But a common pattern that you'll see in testing is adding a test ID data attribute to Dom elements. And Capybara, like, accepts that that's the thing that people do, wants to make your life easier. So you can say, hey. The test ID attribute in my app is data test ID or my test ID or whatever it is. And then now when you say fill in the username field with Joelle, it will look up things by either label or name or ID or test ID using the attribute that I supplied. So that's got me really excited to dig deeper into Capybara selectors. All that being said, relying on test IDs is a bit of an anti pattern. So I'm sort of like, I'm excited that Capybara can do this, and also you probably shouldn't do it. Yeah. Interesting. So it goes in that order of trying to find whatever element you're selecting on. I don't know what the order is. That's a good question. Yeah. So I was thinking a lot about how React testing library, when I need to do something similar and assert on or find and interact with certain …