How to DRY out your RSpec Tests using Shared Examples
By: Parth Modi
Tags: Rspec, Tdd, Ruby, Ruby on Rails, Web Development

“Give me six hours to chop down a tree and I will spend the first four sharpening the axe.” — Abraham Lincoln

When I refactored a project a few weeks ago, I spent most of my time writing specs. After writing several similar test cases for some APIs, I started to wonder whether I might be able to get rid of a lot of this duplication.

So I threw myself into reading up on the best practices for DRYing up tests (Don’t Repeat Yourself). And that’s how I came to know of shared examples and shared contexts .

In my case, I ended up using shared examples. And here’s what I’ve learned so far from applying these.

When you have multiple specs that describe similar behavior, it might be better to extract redundant examples into shared examples and use them in multiple specs.

Suppose you have two models User and Post, and a user can have many posts. Users should be able to view list of users and posts. Creating an index action in the users and posts controllers will serve this purpose.

First, write specs for your index action for the users controller. It will have the responsibility of fetching users and rendering them with proper layout. Then write enough code to make tests pass.

# users_controller_spec.rb

describe "GET #index" do

before do

5.times do

FactoryGirl.create(:user)

end

get :index

end

it { expect(subject).to respond_with(:ok) }

it { expect(subject).to render_template(:index) }

it { expect(assigns(:users)).to match(User.all) }

end # users_controller.rb

class UsersController < ApplicationController

....

def index

@users = User.all

end

....

end

Typically, the index action of any controller fetches and aggregates data from few resources as required. It also adds pagination, searching, sorting, filtering and scoping.

Finally, all these data are presented to views via HTML, JSON, or XML using APIs. To simplify my example, the index actions of controllers will just fetch data, then show them via views.

The same goes for the index action in the posts controller:

describe "GET #index" do

before do

5.times do

FactoryGirl.create(:post)

end

get :index

end

it { expect(subject).to respond_with(:ok) }

it { expect(subject).to render_template(:index) }

it { expect(assigns(:posts)).to match(Post.all) }

end # posts_controller.rb

class PostsController < ApplicationController

....

def index

@posts = Post.all

end

....

end

RSpec tests written for both users and posts controller are very similar. In both controllers we have:

The response code — should be ‘OK’

Both index action should render proper partial or view — in our case index

The data we want to render, such as posts or users

Let’s DRY the specs for our index action by using shared examples .

Where to put your shared examples

I like to place shared examples inside the specs/support/shared_examples directory so that all shared example -related files are loaded automatically.

You can read about other commonly used conventions for locating your shared examples here: shared examples documentation

How to define a shared example

Your index action should respond with 200 success code (OK) and render your index template.

RSpec.shared_examples "index examples" do

it { expect(subject).to respond_with(:ok) }

it { expect(subject).to render_template(:index) }

end

Apart from your it blocks — and before and after your hooks — you can add let blocks, context, and describe blocks, which can also be defined inside shared examples .

I personally prefer to keep shared examples simple and concise, and don’t add contexts and let blocks. The shared examples block also accepts parameters, which I’ll cover below.

How to use shared examples

Adding include_examples "index examples" to your users and posts controller specs includes “index examples” to your tests.

# users_controller_spec.rb

describe "GET #index" do

before do

5.times do

FactoryGirl.create(:user)

end

get :index

end

include_examples "index examples"

it { expect(assigns(:users)).to match(User.all) }

end # similarly, in posts_controller_spec.rb

describe "GET #index" do

before do

5.times do

FactoryGirl.create(:post)

end

get :index

end

include_examples "index examples"

it { expect(assigns(:posts)).to match(Post.all) }

end

You can also use it_behaves_like or it_should_behaves_like instead of include_examples in this case. it_behaves_like and it_should_behaves_like are actually aliases, and work in same manner, so they can be used interchangeably. But include_examples and it_behaves_like are different.

As stated in the official documentation:

include_examples — includes examples in the current context

— includes examples in the current context it_behaves_like and it_should_behave_like include the examples in a nested context

Why does this distinction matter?

RSpec’s documentation gives a proper answer:

When you include parameterized examples in the current context multiple times, you may override previous method definitions and last declaration wins.

So when you face situation where parameterized examples contain methods that conflict with other methods in same context, you can replace include_examples with it_behaves_like method. This will create a nested context and avoid this kind of situations.

Check out the following line in your users controller specs, and posts controller specs:

it { expect(assigns(:users)).to match(User.all) }

it { expect(assigns(:posts)).to match(Post.all) }

Now your controller specs can be re-factored further by passing parameters to shared example as below:

# specs/support/shared_examples/index_examples.rb # here assigned_resource and resource class are parameters passed to index examples block

RSpec.shared_examples "index examples" do |assigned_resource, resource_class|

it { expect(subject).to respond_with(:ok) }

it { expect(subject).to render_template(:index) }

it { expect(assigns(assigned_resource)).to match(resource_class.all) }

end

Now, make following changes to your users and posts controller specs:

# users_controller_spec.rb

describe "GET #index" do

before do

...

end

include_examples "index examples", :users, User.all

end # posts_controller_spec.rb

describe "GET #index" do

before do

...

end

include_examples "index examples", :posts, Post.all

end

Now controller specs look clean, less redundant and more importantly, DRY. Furthermore, these index examples can serve as basic structures for designing the index action of other controllers.

Conclusion

By moving common examples into a separate file, you can eliminate duplication and improve the consistency of your controller actions throughout your application. This is very useful in case of designing APIs, as you can use the existing structure of RSpec tests to design tests and create APIs that adhere to your common response structure.

Mostly, when I work with APIs, I use shared examples to provide me with a common structure to design similar APIs.