Selleo Labs spółka z o.o.

My diverse educational background allows me to approach software development problems from different sides and angles. I have bachelor degrees in Sociology and IT in Business. I am an agile Team Leader and Project Manager. Sport and Combat training allowed me to learn that success comes with hard work. Along came the self-improvement, loyalty, discipline and self-control.

**ABOUT MY TEAM** “...there is no **I** in **Team**”

My Team has an in-depth and long term experience (**4 years** on average) and currently consists of **9 members**. We specialize in **Ruby on Rails**, **React.js**, **React Native** and **Node.js**. We work from **one** **office** which guarantees close and **successful** **cooperation**. We use the following communication tools: Slack, Pivotal Tracker, Trello, Jira and Google Hangouts.

***"With few exceptions the best players are the hardest workers"***

I love coding and I **enjoy** **solving** **various** **business** **problems** with my programming skills.

I'm a passionate COO dedicated to helping my clients craft state-of-the-art software solutions. With over 15 years in the industry, I've evolved from coder to tech leader, gaining hands-on experience in building various platforms and leading teams of many developers. This journey has empowered me to mentor emerging leaders and share insights on team-building, successful project management, and outsourcing. In the dynamic realm of tech, I'm committed to shaping the future and inspiring others to push boundaries alongside me.

Ireneusz Skrobiś

\[TOC\]

In the last [article](https://selleo.com/blog/graphql-mutations-in-ruby-on-rails) we added a few GraphQL mutations to our test application. It is time to create automated tests for each of them. But first things first, we need to set up RSpec in order to write better specs.

## RSpec and FactoryBot

Installing **Rspec** and Factory Bot are trivial. First, you have to add those gems to your `Gemfile`:
<Gist id="76cd1fd2fe3e0c03b86a71c54e9b0f4d" />

run `bundle install`

and then run `rails generate rspec:install`

The last thing I recommend to do is adding this line to `spec/rails_helper.rb`
<Gist id="21b07da7adaea3732a0d950391ce162e" />

Thanks to that line we will be able to use shortened syntax for building and creating objects using factories. It means that instead of `FactoryBot.create(:book)` we will be able to simply write `create(:book)`.

## Factories

I mentioned that we will be able to create objects easily thanks to FactoryBot. But in order to have this possibility, we have to define those factories first. We need to create two of them:

`specs/factories/author_factory.rb`
<Gist id="2fbae29f87575e6f0360a4d786e01583" />

`specs/factories/book_factory.rb`
<Gist id="50c01305943ccac7905fd9233ae0f746" />

Now we have everything in place and we are able to start writing specs. But please note that for now, we will cover only the happy paths.

## CreateBook spec

During the creation of the object, the most important assertion we can write is checking if the object is created and its fields in the database are correct. But when we are **testing GraphQL** endpoint we also want to make sure that it returns the proper object. Knowing all that, let’s take a look at the final version of our test. Following the RSpec convention, we are going to save our file in `specs` folder, in the same tree directory as the original file. In short, we save our spec in `specs/graphql/mutations/books/create_book_spec.rb`
<Gist id="dab549d11546cc69ba75c24b4bfefe83" />

As you can see, we test `.resolve` method and we check the things that I mentioned earlier, so writing and returning the object. There are two separates specs and we want to use the same query for both of them. Because of that, we define the `query` function when we pass the arguments that matter for us. In this case, we only need to pass `author_id`.

## UpdateBook spec

In `updateBook` spec we are going to test if an object is changed after the operation and if the correct object is returned. The code will be really similar to the previous one and we place it in `specs/graphql/mutations/books/update_book_spec.rb`
<Gist id="e0c4a19b6902fa7a8bf43865be086049" />

## DestroyBook spec

The last spec will be written for `destroyBook` mutation. We will focus on checking if the object is removed and if we return removed object after the action is finished. As you probably guessed, we save the code in `specs/graphql/mutations/books/update_book_spec.rb`
<Gist id="f51b28faaca349348d2165d76d3c8944" />

## Summary

Writing the specs for GraphQL mutations isn’t that different from writing specs for the controller’s actions. The only difference might be defining the `query` method. I highly encourage you to use `<<\~` to write a multiline query and increase the readability. Other than that, you simply have to focus on things and edge cases you want to cover in your specs. That’s all. Happy coding!

In the last article we added a few GraphQL mutations to our test application. It is time to create automated tests for each of them. But first things first, we need to set up `RSpec` in order to write better specs.

CTOs

Founders

Read Our Blog.
Make better products with us.

Knowledge hub

Business

Technology

Explore our latest articles

Testing GraphQL Mutations In Ruby On Rails With RSpec

SaaS Founder Starter Academy