configure API mode Rspec Ruby On Rails bagian 1

RSpec is a unit testing framework for the Ruby programming language. RSpec differs from traditional xUnit frameworks such as JUnit because RSpec is a behavior-based development tool. This means that tests written in RSpec focus on the “behavior” of the application under test.

RSpec is a DSL for creating executable examples of how code should behave, organized into groups. He uses the words “describe” and “that” so we can express concepts like conversation:

"Describe an account when it is first opened."
"It has a balance of zero."

1. configure and install ror and rspec

Create a new application with the following command

rails _7.0.1_ new sample_unit_test --api -d postgresql

go to the directory we created

 cd sample_unit_test 

open the Gemfile and add the ‘rspec-rails’ gem

go back to terminal and run

 bundle install 

create a database with run

 bundle exec rake db:create 

configure rspec on rails with the following command

bundle exec rails generate rspec:install  

2. Create a client model and raw features whose functionality we will test

 bundle exec rails g scaffold customer name:string phone:bigint email:string address:text

bundle exec rake db:migrate

edit app/models/customer.rb add validation

 class Customer < ApplicationRecord  
  validates :name, :email, presence: true  
 end  

3. update rspec file
When we run the scaffold ror command, it will also automatically create a test file

To test the customer controller, edit the file in spec/requests/customers_spec.rb

default isi file dari customer test request

Because the content is still empty, we need to fill in the correct attributes and use the “fake” gem to help match the data.

let(:valid_attributes) do  
   { name: Faker::Name.name,  
    phone: Faker::Number.number(digits: 12),  
    email: Faker::Internet.email,  
    address: Faker::Address.street_address }  
  end  
   
  let(:invalid_attributes) do  
   { name: nil,  
    phone: nil,  
    email: Faker::Internet.email,  
    address: Faker::Address.street_address }  
  end  
   
  let(:valid_headers) do  
   {}  
  end 

valid headers are left empty because this tutorial does not use security tokens

after adding valid_attributes and invalid_attributes try testing with the following command

bundle exec rspec spec/requests/customers_spec.rb 

Image after updating valid and invalid attributes

In the error description there are two processes waiting because there is a time skip in the update section
reopen the following file

spec/requests/customers_spec.rb 

Updated part of Gambar’s default code

The skipped section must be replaced according to the description of the new attribute, i.e. the data content. new_attributes To replace the old data, the content looks like the code below

    let(:new_name) { Faker::Name.name }  
    let(:new_attributes) do  
     { name: new_name,  
      phone: Faker::Number.number(digits: 12),  
      email: Faker::Internet.email,  
      address: Faker::Address.street_address }  
    end 

    it 'updates the requested customer' do  
     customer = Customer.create! valid_attributes  
     patch customer_url(customer),  
        params: { customer: new_attributes }, headers: valid_headers, as: :json  
     customer.reload  
     expect(customer.name).to eq(new_name)  
    end 

bundle exec rspec spec/requests/customers_spec.rb 

Image of passed test results without failure

Test the customer model update spec/models/customer_spec.rb as follows, then run the tests

 require 'rails_helper'  
 RSpec.describe Customer, type: :model do  
  it 'is not valid without a name' do  
   customer = Customer.new(name: nil)  
   expect(customer).to_not be_valid  
  end  
  it 'is not valid without a email' do  
   customer = Customer.new(email: nil)  
   expect(customer).to_not be_valid  
  end  
 end 

testing for client models here is just a validation, in fact there can be a lot depending on the content of the model