Fixture and factory usage in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load fixtures in a Rails test.

Ruby on Rails

fixtures :[1]

Drag options to blanks, or click blank then click option'

Amodels

Busers

Ccontrollers

Dviews

Attempts:

3 left

💡 Hint

Common Mistakes

Using controller or view names instead of fixture names.

Trying to load fixtures that don't exist.

In Rails tests, you load fixtures by specifying the fixture name, such as users for user data.

2fill in blank

medium

Complete the factory definition to create a user with FactoryBot.

Ruby on Rails

factory :user do
  [1] { "[e-mail]" }
end

Drag options to blanks, or click blank then click option'

Aname

Bpassword

Cusername

Demail

Attempts:

3 left

💡 Hint

Common Mistakes

Using name or username instead of email.

Forgetting to use curly braces for the block.

The email attribute is commonly set in a user factory to provide a unique email address.

3fill in blank

hard

Fix the error in the factory usage to create a user instance.

Ruby on Rails

user = FactoryBot.[1](:user)

Drag options to blanks, or click blank then click option'

Acreate

Bmakes

Cbuilds

Dgenerate

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like builds or makes.

Confusing build (which does not save) with create.

The correct method to create and save a factory object is create.

4fill in blank

hard

Fill both blanks to define a fixture file path and load it in a test.

Ruby on Rails

fixtures :[1]

file_path = Rails.root.join('test', 'fixtures', '[2].yml')

Drag options to blanks, or click blank then click option'

Ausers

Bposts

Ccomments

Dprofiles

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for fixture and file path.

Misspelling the fixture file name.

The fixture name and file path must match. Here, users is used for both.

5fill in blank

hard

Fill all three blanks to create a factory with a sequence and use it in a test.

Ruby on Rails

factory :user do
  [1] :email do |[2]|
    "user[2]@example.com"
  end
end

user = FactoryBot.[3](:user)

Drag options to blanks, or click blank then click option'

Asequence

Bn

Ccreate

Demail

Attempts:

3 left

💡 Hint

Common Mistakes

Using email instead of sequence.

Forgetting to use the block variable n.

Using build instead of create when saving is needed.

Use sequence to generate unique emails with a number n. Then use create to make the user.

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