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.