Rails plugin testing guide

A surprisingly large number of plugins have no tests at all. Part of the reason might be that writing a plugin test is a little bit harder than writing a normal unit test.

Simplifies plugin testing by creating an isolated Rails environment that simulates its usage in a real application

Unfortunately, by default plugin tests are pretty bland. They use the plain unit test suite supplied by Ruby, and not any of the extended Rails test framework. This will leave our plugin’s test classes with no access to fixtures, database.yml conf...

Passing the --profile flag to RSpec produces some additional output, namely the running times of the ten slowest examples in your specs.

After 2 1/2 years of blood, sweat, tears, and the occasional Jägermeister, I’m finally officially announcing a project I’ve been quietly working on: state_machine.

Here are eight things my team has found to be true after working with Cucumber for about 6 months.

When Rails releases a new version of their gems, they also release a number of npm packages
like @rails/activestorage or @rails/actioncable.

Unfortunately Rails uses up to 4 digits for their gem version, while npm only allows 3 digits and a [...

See our new comprehensive guide for upgrading every Rails 2 version ever.

A/Bingo is a Ruby on Rails A/B testing framework written as a plugin.

Where there was once a consistent API to manipulate and hook into the lifecycle of a persistent object, plugins must now perform very careful checks whether an object supports more advanced traits like transactions, observers or dirty attribute tr...