Fixture and factory usage in Ruby on Rails - Mini Project: Build & Apply

Fixture and Factory Usage in Rails Testing

📖 Scenario: You are building a simple Rails application to manage books and authors. You want to write tests that use fixtures and factories to create test data easily and reliably.

🎯 Goal: Learn how to set up fixtures and factories in Rails tests and use them to create test data for Author and Book models.

📋 What You'll Learn

Create a fixture file for authors with exact entries

Create a factory for books with specific attributes

Write a test that uses the author fixture and book factory

Use the factory to create a book linked to the fixture author

💡 Why This Matters

🌍 Real World

Fixtures and factories help create consistent test data in Rails applications, making tests reliable and easier to maintain.

💼 Career

Understanding how to use fixtures and factories is essential for Rails developers writing automated tests to ensure code quality and prevent bugs.

1

Create an author fixture

Create a fixture file named authors.yml with an author entry called jane_doe having name: "Jane Doe" and email: "[e-mail]".

Ruby on Rails

# Create authors.yml fixture with jane_doe author
# Your code here

Hint

Fixtures are YAML files placed in test/fixtures/. Use the exact keys and values as shown.

2

Create a book factory

Create a factory for the Book model in test/factories/books.rb with a title set to "Sample Book" and an association to author.

Ruby on Rails

jane_doe:
  name: "Jane Doe"
  email: "[e-mail]"

# Define a factory for Book with title and author association
# Your code here

Hint

Use FactoryBot syntax to define a factory with a title attribute and link it to the author model.

3

Write a test using fixture and factory

In a test file, write a test method named test_book_creation that loads the jane_doe author fixture and uses the book factory to create a book linked to this author.

Ruby on Rails

jane_doe:
  name: "Jane Doe"
  email: "[e-mail]"

FactoryBot.define do
  factory :book do
    title { "Sample Book" }
    association :author
  end
end

# Write test_book_creation method using jane_doe fixture and book factory
# Your code here

Hint

Use authors(:jane_doe) to access the fixture and FactoryBot.create to make a book linked to that author.

4

Complete test setup with required includes

Add the necessary require statement for factory_bot_rails in the test file to enable factory usage.

Ruby on Rails

jane_doe:
  name: "Jane Doe"
  email: "[e-mail]"

FactoryBot.define do
  factory :book do
    title { "Sample Book" }
    association :author
  end
end

# Add require statement for factory_bot_rails
require "test_helper"

class BookTest < ActiveSupport::TestCase
  fixtures :authors

  def test_book_creation
    author = authors(:jane_doe)
    book = FactoryBot.create(:book, author: author)
    assert_equal "Sample Book", book.title
    assert_equal author, book.author
  end
end

Hint

Factories need the factory_bot_rails gem required in test files to work properly.

Practice

1. What is the main difference between fixtures and factories in Rails testing?

easy

A. Fixtures use static YAML files, while factories generate data dynamically with Ruby code.

B. Fixtures are faster to write than factories.

C. Factories require no setup, but fixtures need database cleaning.

D. Factories store data in YAML files, fixtures use Ruby code.

Solution

1. Step 1: Understand fixtures data source

   Fixtures load test data from static YAML files before tests run.

2. Step 2: Understand factories data generation

   Factories create test data dynamically using Ruby code during test execution.

3. Final Answer:

   Fixtures use static YAML files, while factories generate data dynamically with Ruby code. -> Option A

4. Quick Check:

   Fixtures = YAML, Factories = Ruby code [OK]

Hint: Fixtures = YAML files, factories = Ruby code [OK]

Common Mistakes:

• Confusing fixtures as dynamic data generators
• Thinking factories use YAML files
• Assuming fixtures are created with Ruby code

2. Which of the following is the correct syntax to define a factory for a User model using FactoryBot?

easy

A. factory :user do
name { "Alice" }
end

B. define_factory :user do
name "Alice"
end

C. FactoryBot.define do
factory :user do
name { "Alice" }
end
end

D. factory :user {
name: "Alice"
}

Solution

1. Step 1: Recognize FactoryBot syntax

   FactoryBot factories are defined inside a block passed to FactoryBot.define.

2. Step 2: Check block and attribute syntax

   Attributes use curly braces with Ruby code, e.g., name { "Alice" }.

3. Final Answer:

   FactoryBot.define do factory :user do name { "Alice" } end end -> Option C

4. Quick Check:

   FactoryBot.define + block + attribute with braces [OK]

Hint: FactoryBot.define block wraps factory definitions [OK]

Common Mistakes:

• Omitting FactoryBot.define block
• Using wrong attribute syntax without braces
• Using invalid factory syntax like curly braces for block

3. Given the following factory and test code, what will user.name output?

FactoryBot.define do
  factory :user do
    name { "Bob" }
  end
end

user = FactoryBot.create(:user)

medium

A. "Alice"

B. nil

C. Raises an error because name is missing

D. "Bob"

Solution

1. Step 1: Understand factory attribute assignment

   The factory sets the name attribute to "Bob" using a block.

2. Step 2: FactoryBot.create builds and saves user

   Calling create(:user) builds a user with name "Bob" and saves it.

3. Final Answer:

   "Bob" -> Option D

4. Quick Check:

   Factory attribute value = "Bob" [OK]

Hint: Factory attribute blocks set values directly [OK]

Common Mistakes:

• Assuming default name is nil
• Confusing create with build (create saves)
• Expecting name to be "Alice" without definition

4. You have a fixture file users.yml with a user named john. In your test, you write users(:john) but get an error. What is a likely cause?

medium

A. The test database is not migrated.

B. The fixture file is not loaded or declared in the test setup.

C. You must use FactoryBot.create instead of fixtures.

D. The user named john is misspelled in the fixture file.

Solution

1. Step 1: Check fixture loading in test

   Fixtures must be declared or loaded for the test to access them.

2. Step 2: Confirm fixture file presence and naming

   If the fixture file exists but is not loaded, users(:john) will raise an error.

3. Final Answer:

   The fixture file is not loaded or declared in the test setup. -> Option B

4. Quick Check:

   Fixtures must be loaded to use named references [OK]

Hint: Load fixtures before using named references [OK]

Common Mistakes:

• Assuming misspelling without checking loading
• Thinking FactoryBot is required instead of fixtures
• Ignoring fixture loading setup in test

5. You want to create multiple users with different emails using factories in a test. Which approach correctly creates 3 users with unique emails?

hard

A. factory :user do
sequence(:email) { |n| "user#{n}@example.com" }
end

users = 3.times.map { FactoryBot.create(:user) }

B. factory :user do
email "[e-mail]"
end

users = 3.times.map { FactoryBot.create(:user) }

C. factory :user do
email { "[e-mail]" }
end

users = FactoryBot.create_list(:user, 3)

D. factory :user do
email { "[e-mail]" }
end

users = FactoryBot.build(:user, 3)

Solution

1. Step 1: Understand sequence usage in factories

   Using sequence(:email) generates unique emails for each created user.

2. Step 2: Confirm multiple user creation with unique emails

   Calling FactoryBot.create inside a loop with sequence ensures 3 users with different emails.

3. Final Answer:

   factory :user do sequence(:email) { |n| "user#{n}@example.com" } end users = 3.times.map { FactoryBot.create(:user) } -> Option A

4. Quick Check:

   Sequence + create loop = unique users [OK]

Hint: Use sequence for unique attributes in factories [OK]

Common Mistakes:

• Using static email causing duplicates
• Using build instead of create (no DB save)
• Not using sequence for unique values