Flakiness on browser-based system tests (integration tests) in Ruby on Rails may have a lot of different reasons. One is scrolling, which may be slowed down by browser setup (smooth scrolling), JavaScript callbacks which result in some kind of events like for animations, etc.
A lot of Ruby on Rails applications created with Ruby on Rails version 5.x or 6.x or even upgraded from the previous versions are using webpacker as their primary asset pipeline. But now as webpacker has retired, it is time to move on.
A lot of Ruby on Rails applications created with Ruby on Rails version 5.x or 6.x or even upgraded from the previous versions are using webpacker as their primary asset pipeline. But now as webpacker has retired, it is time to move on.
Before removing sprockets-rails from dependencies of your Ruby on Rails project, check whether you are surfing images or fonts using sprockets through assets paths like: app/assets/images app/assets/fonts … or any other assets except Style Sheets (CSS): app/assets/js If you are using cssbundling-rails the sprockets default path for Style Sheets is used by default:
Recently RuboCop started to blame my assert something.booked? style tests in minitest and telling me this: Minitest/AssertPredicate: Prefer using `assert_predicate(something, :booked?)`. I’ve looked for the corresponding Pull Request and also checked the final Rubocop Minitest Style Guide: Assert Predicate. According to the documentation, we can read: