Model tests in Ruby on Rails - Step-by-Step Execution

Concept Flow - Model tests

Write model code

↓

Write test cases

↓

Run tests

↓

Tests pass?

No→Fix code or tests

Yes↓

Model behavior verified

This flow shows writing model code, creating tests, running them, and fixing issues until tests pass.

Execution Sample

Ruby on Rails

class User < ApplicationRecord
  validates :email, presence: true
end

user = User.new
assert user.valid? == false

This code defines a User model with an email validation and tests if a user is valid.

Execution Table

Step	Action	Input/State	Output/Result
1	Create User instance	User.new(email: nil)	User object with email=nil
2	Validate user	user.valid?	false (email missing)
3	Set email	user.email = '[e-mail]'	email set
4	Validate user again	user.valid?	true (email present)
5	Test assertion	assert user.valid?	passes
6	Run test suite	all tests	success
7	End	tests passed	Model behavior confirmed

💡 Tests pass confirming model validations work as expected

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
user.email	nil	nil	'[e-mail]'	'[e-mail]'
user.valid?	N/A	false	true	true

Key Moments - 3 Insights

Why does user.valid? return false at first?

Because the email attribute is nil and the model requires email presence, as shown in execution_table step 2.

What changes user.valid? to true?

Assigning a valid email string to user.email makes validation pass, as seen in step 4.

Why run tests after validation?

Running tests confirms the model behaves correctly and prevents future bugs, shown in steps 5 and 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is user.valid? at step 2?

A nil

B true

C false

D error

💡 Hint

Check the 'Output/Result' column at step 2 in execution_table

At which step does the user get a valid email assigned?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Look at the 'Action' and 'Input/State' columns in execution_table

If the email validation was removed, what would user.valid? return at step 2?

A false

B true

C nil

D error

💡 Hint

Without validation, user.valid? would not fail due to missing email, see variable_tracker for validation effect

Concept Snapshot

Model tests check if your data rules work.
Write validations in model (e.g., presence).
Write tests creating model instances.
Run tests to confirm model behaves right.
Fix code/tests if tests fail.
Repeat until tests pass.

Full Transcript

Model tests in Rails help ensure your data rules work correctly. You write validations in your model, like requiring an email. Then you write tests that create model instances and check if they are valid. Running these tests shows if your model behaves as expected. If tests fail, you fix your code or tests and run again until all tests pass. This process helps catch errors early and keeps your app reliable.

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