Model tests in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of model tests in Rails?

Model tests check that the data and business logic in your Rails models work correctly. They ensure validations, associations, and methods behave as expected.

beginner

How do you test a validation in a Rails model?

You create a test that tries to save a model with invalid data and check that it does not save and adds the correct error messages.

intermediate

What is a fixture in Rails testing?

A fixture is a sample data file used to set up known data in the test database before running tests. It helps tests run with consistent data.

intermediate

Why should model tests be fast and isolated?

Fast and isolated tests help you quickly find problems and run tests often. They focus only on the model without depending on other parts like the UI or controllers.

beginner

How do you test a custom method in a Rails model?

You write a test that calls the method on a model instance and checks that it returns the expected result or changes the model state correctly.

Which Rails testing framework is commonly used for model tests?

A RSpec

B Minitest

C Capybara

D Selenium

RSpec and Minitest are popular testing frameworks in Rails for writing readable and expressive model tests.

What does a validation test usually check in a Rails model?

A That the model saves with valid data

B That the model has associations

C That the model fails to save with invalid data

D That the model has database indexes

Validation tests check that invalid data prevents saving and adds errors.

Which method is used to create a test instance of a model in Rails tests?

A Model.new

B Model.create

C Model.build

D Model.save

Model.new creates a new instance without saving, useful for testing validations before saving.

What is the role of fixtures in Rails model tests?

A To provide sample data for tests

B To style the test output

C To mock external APIs

D To run tests in parallel

Fixtures provide sample data loaded into the test database before tests run.

Why should model tests avoid relying on the UI or controllers?

A Because models do not interact with databases

B To keep tests fast and focused on model logic

C Because controllers handle validations

D Because UI tests are easier

Model tests should be fast and isolated to quickly find issues in model logic.

Explain how to write a test for a validation in a Rails model.

Think about what happens when you try to save wrong data.

Describe the benefits of using fixtures in Rails model tests.

Fixtures help set up the test environment.

Practice

1. What is the main purpose of model tests in a Rails application?

easy

A. To check data validations and model methods work correctly

B. To test the user interface layout

C. To verify database server performance

D. To check network connectivity

Solution

1. Step 1: Understand what model tests cover

   Model tests focus on the data layer, ensuring validations and methods behave as expected.

2. Step 2: Differentiate from other test types

   User interface and network tests are handled by other test types, not model tests.

3. Final Answer:

   To check data validations and model methods work correctly -> Option A

4. Quick Check:

   Model tests = data rules and logic [OK]

Hint: Model tests check data rules and methods only [OK]

Common Mistakes:

• Confusing model tests with UI tests
• Thinking model tests check server or network
• Assuming model tests check database performance

2. Which of the following is the correct syntax to test a presence validation on a Rails model attribute name using RSpec?

easy

A. expect(user).to validate_presence(:name)

B. expect(user).to be_validates_presence_of(:name)

C. expect(user).to have_presence_validation(:name)

D. expect(user).to validate_presence_of(:name)

Solution

1. Step 1: Recall RSpec validation matcher syntax

   The correct matcher is validate_presence_of(:attribute) used with expect(model).

2. Step 2: Check each option for exact syntax

   Only expect(user).to validate_presence_of(:name) matches the correct RSpec syntax for presence validation.

3. Final Answer:

   expect(user).to validate_presence_of(:name) -> Option D

4. Quick Check:

   RSpec presence validation = validate_presence_of [OK]

Hint: Use validate_presence_of matcher exactly in RSpec [OK]

Common Mistakes:

• Using incorrect matcher names
• Adding extra words like 'be_' or 'have_'
• Missing the '_of' suffix in matcher

3. Given this model test snippet:

RSpec.describe User, type: :model do
  it 'is invalid without email' do
    user = User.new(email: nil)
    expect(user).not_to be_valid
  end
end

What will this test check?

medium

A. That a User with an email is invalid

B. That the User model has a method called email

C. That a User without an email is invalid

D. That the User model saves successfully without email

Solution

1. Step 1: Analyze the test setup

   The test creates a User with email: nil, meaning no email is given.

2. Step 2: Understand the expectation

   The test expects user to NOT be valid, so it checks that missing email makes the user invalid.

3. Final Answer:

   That a User without an email is invalid -> Option C

4. Quick Check:

   Missing email -> invalid user [OK]

Hint: Check what attribute is nil and expected validity [OK]

Common Mistakes:

• Misreading the test as checking presence of method
• Thinking it tests saving instead of validation
• Confusing valid and invalid expectations

4. You wrote this model test:

it 'validates presence of title' do
  post = Post.new(title: '')
  expect(post).to be_valid
end

Why does this test fail?

medium

A. Because title is empty but test expects valid

B. Because Post.new requires a title argument

C. Because be_valid is not a valid matcher

D. Because the test is missing a database save

Solution

1. Step 1: Understand the test setup

   The test creates a Post with an empty string for title.

2. Step 2: Check the expectation vs validation

   If the model validates presence of title, empty string is invalid, but test expects valid, causing failure.

3. Final Answer:

   Because title is empty but test expects valid -> Option A

4. Quick Check:

   Empty title ≠ valid if presence validated [OK]

Hint: Empty string fails presence validation, expect invalid [OK]

Common Mistakes:

• Assuming empty string counts as present
• Thinking be_valid matcher is wrong
• Ignoring validation rules in test

5. You want to test a custom method full_name in your User model that combines first_name and last_name. Which is the best way to write this model test?

hard

A. Write a controller test that calls full_name

B. Create a User with first and last names, then expect user.full_name to equal their combination

C. Check that full_name is validated for presence

D. Test that full_name is a database column

Solution

1. Step 1: Identify what to test for a custom method

   Custom methods should be tested by calling them and checking their return values.

2. Step 2: Choose the test that verifies method output

   Creating a User with names and expecting full_name to return combined string is correct.

3. Final Answer:

   Create a User with first and last names, then expect user.full_name to equal their combination -> Option B

4. Quick Check:

   Test method output by calling it with sample data [OK]

Hint: Test method output by calling it on sample model instance [OK]

Common Mistakes:

• Testing method as if it were a database column
• Confusing validation tests with method tests
• Writing controller tests instead of model tests