Ruby
-
-
Rake without Rails.
A lot of ink has been spilled over how to get “real” unit tests working in Ruby on Rails projects. The first time I encountered it was when Gary Bernhardt and Corey Haines started the “fast specs” meme. -
-
-
-
Good migrations.
We wrote a gem! It’s called good_migrations and we recommend you add it to all of your Ruby on Rails projects and subsequently forget about it. Just do it. There’s no reason we can see not to blindly copy-paste this command right now: -
Concurrent Ruby 1.0 Has Been Released!
Today I’m excited to announce that I’ve released version 1.0 of my Concurrent Ruby gem! One of the reasons I came to work at Test Double is the dedication and passion the company has for open source. -
Arcane knowledge needed to write a test.
A single test This weekend I was reminded how complex (and in some cases, convoluted) typical test setup is for Rails applications. The steps below were all necessary in my case, but please don’t read into this list any criticisms of these tools' excellent open source maintainers. -
Healthy migration habits.
ActiveRecord migrations are a killer feature of Ruby on Rails. The feature is very well-implemented, it’s easy to use, and countless teams have benefited from it. Before Rails, most teams I encountered were in the habit of making incredibly error-prone ad hoc changes to each of their application’s databases. -
2 of 2
