Welcome to our lesson on implementing request and authentication tests for the ToDo service in your Ruby on Rails application. Unit testing is an essential part of software development, helping you ensure that your application behaves as expected and is free from bugs. In this lesson, we will continue putting our focus on using RSpec to write and run tests for various functions of our ToDo service, such as creating and retrieving todos.

By the end of this lesson, you will be able to write comprehensive unit tests for your ToDo service and understand how these tests contribute to the stability and reliability of your application.

Request specs in RSpec allow you to simulate HTTP requests to your application and inspect the responses. Let’s write tests for the ToDo model.

• describe "POST /todos" do: Starts testing "POST /todos".
• it "creates a new todo" do: Tests creation of a new todo.
• todo_params = { title: 'Test Todo', description: 'Test Desc' }: Defines new todo parameters.
• post todos_path, params: { todo: todo_params }, headers: { 'Authorization': "Bearer #{token}" }: Sends a POST request with authentication.
• expect(response).to have_http_status(:created): Checks for 201 Created status.
• todo = JSON.parse(response.body): Parses response to JSON.
• expect(todo['title']).to eq('Test Todo'): Verifies the todo's title.

Continuing in the same file, add the following test:

• require 'rails_helper': Sets up test environment.
• RSpec.describe "Todos", type: :request do: Begins "Todos" request tests.
• let(:user) ... }: Creates a user for testing.
• let(:token) ... ) }: Generates JWT token.
• describe "GET /todos" do: Tests "GET /todos".
• it "returns all todos" do: Checks fetching of todos.
• get todos_path, ...: Sends GET request with token.
• expect(response).to have_http_status(:success): Expects 200 OK status.
• todos = JSON.parse(response.body): Parses response.
• expect(todos.length).to eq(1): Verifies todos count.

Authentication is crucial for securing endpoints. Let's write tests for user registration and login.

Create a new file named spec/requests/authentication_spec.rb and add the following test:

• require 'rails_helper': Sets up test environment.
• RSpec.describe "Authentication", type: :request do: Begins authentication tests.
• describe "POST /register" do: Tests registration.
• it "registers a new user" do: Verifies user registration.
• user_params = { ... }: Sets registration data.
• post register_path, ...: Sends POST request.
• expect(response).to have_http_status(:created): Expects 201 Created.
• message = JSON.parse(response.body): Parses response.
• expect(message['message']).to eq('User created successfully'): Checks success message.

Add the following test:

• describe "POST /login" do: Tests login endpoint.
• let!(:user) ... }: Prepares a user for login.
• it "logs in a user" do: Validates user login.
• login_params = { ... }: Defines login credentials.
• post login_path, ...: Sends POST request.
• expect(response).to have_http_status(:ok): Expects 200 OK.
• token = JSON.parse(response.body)['token']: Extracts token.
• expect(token).to be_present: Checks token presence.

We’ve covered a lot in this lesson: you learned how to write request specs for ToDo and authentication endpoints. These tests are vital for ensuring that your application functions correctly and securely.

As this is the last lesson of the course, I want to congratulate you on your progress. You now have a strong foundation in securing and testing your Ruby on Rails app. Next, practice what you’ve learned by completing the exercises provided. Thank you for completing the course, and happy coding!