Rails actions default on using record IDs. But what if we want to change the URL to something prettier, something that doesn’t leak the record ID in the database?
There are several reasons I like Rails’ fixtures for testing. One such reason is that modeling a small world gives you instant data for seeding your database.
Want to run your system tests headless? And why not both ways? Here’s how to extend Rails tasks to run your system tests with the driver of your choice.
Rails system tests often depend on input and CSS selectors. To make our tests more maintainable, we can isolate layout changes within page objects.
Turbo can largely simplify our front-end needs to achieve a single-page application feel. If you have ever wondered how to do a single attribute in-place update with Turbo, this post is for you.