Why testing is integral to Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to write a simple test method in Rails using Minitest.

Ruby on Rails

def test_[1]_is_valid
  assert true
end

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

Auser_creation

Bcontroller_response

Cmodel_validation

Ddatabase_connection

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces or special characters in the test method name.

Not starting the method name with 'test_'.

The test method name should describe what is being tested. Here, model_validation is a common test name in Rails.

2fill in blank

medium

Complete the code to assert that a Rails model is invalid without a required attribute.

Ruby on Rails

user = User.new(name: nil)
assert_equal [1], user.valid?

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

Afalse

Bnil

Ctrue

Dempty

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'true' instead of 'false' in the assertion.

Confusing the meaning of 'valid?' method.

The test checks that the user is not valid when the name is missing, so we use assert_equal false, user.valid?.

3fill in blank

hard

Fix the error in the test that checks the response status of a controller action.

Ruby on Rails

get :index
assert_response [1]

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

A404

B302

C500

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using 404 (not found) or 500 (server error) incorrectly.

Confusing redirect status 302 with success 200.

The index action should respond with HTTP status 200 (OK) if successful.

4fill in blank

hard

Fill both blanks to create a test that checks a model's attribute presence validation.

Ruby on Rails

test "[1] presence" do
  user = User.new([2]: nil)
  assert_not user.valid?
end

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

Aname

Bemail

Cpassword

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching the test name and attribute name.

Using an attribute that is not validated for presence.

This test checks that the name attribute must be present for the user to be valid.

5fill in blank

hard

Fill all three blanks to write a test that checks a controller redirects after creating a record.

Ruby on Rails

post :create, params: { user: { [1]: "test", [2]: "[e-mail]" } }
assert_redirected_to [3]_path

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

Aname

Bemail

Cuser

Droot

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong attribute names in params.

Asserting redirect to an unrelated path.

The test posts user data with name and email, then asserts the redirect goes to the user_path.

Practice

1. Why is testing considered an integral part of Rails development?

easy

A. It makes the app run faster in production.

B. It helps catch bugs early and ensures the app works as expected.

C. It automatically writes code for you.

D. It replaces the need for writing documentation.

Solution

1. Step 1: Understand the purpose of testing in Rails

   Testing is used to verify that the app behaves correctly and to find bugs early.

2. Step 2: Evaluate the options based on Rails testing goals

   Only It helps catch bugs early and ensures the app works as expected. correctly states that testing helps catch bugs early and ensures expected behavior.

3. Final Answer:

   It helps catch bugs early and ensures the app works as expected. -> Option B

4. Quick Check:

   Testing purpose = catch bugs early [OK]

Hint: Testing finds bugs early and confirms app behavior [OK]

Common Mistakes:

• Thinking testing speeds up production
• Believing testing writes code automatically
• Confusing testing with documentation

2. Which of the following is the correct way to run all tests in a Rails application from the command line?

easy

A. rails start tests

B. rails run tests

C. rails execute tests

D. rails test

Solution

1. Step 1: Recall the Rails command to run tests

   The standard command to run all tests in Rails is rails test.

2. Step 2: Check each option for correctness

   Only rails test uses the correct Rails command syntax to run tests.

3. Final Answer:

   rails test -> Option D

4. Quick Check:

   Run tests command = rails test [OK]

Hint: Use 'rails test' to run all tests in Rails [OK]

Common Mistakes:

• Using incorrect commands like 'rails run tests'
• Confusing 'rails start' with test commands
• Adding extra words to the command

3. Given this test code snippet in Rails:

test "should save user" do
  user = User.new(name: "Alice")
  assert user.save
end

What will happen if the user fails to save due to validation errors?

medium

A. The test will pass because the user object was created.

B. The test will be skipped automatically.

C. The test will fail because assert user.save expects true.

D. The test will raise a syntax error.

Solution

1. Step 1: Understand what assert user.save does

   This line checks if user.save returns true, meaning the user saved successfully.

2. Step 2: Consider the case when save fails

   If validations fail, user.save returns false, causing the assertion to fail and the test to fail.

3. Final Answer:

   The test will fail because assert user.save expects true. -> Option C

4. Quick Check:

   Failed save = test fails [OK]

Hint: assert expects true; false means test failure [OK]

Common Mistakes:

• Assuming test passes if object exists
• Thinking assertion causes syntax error
• Believing tests skip on failure

4. You wrote this test in Rails:

test "should create post" do
  post = Post.new(title: "Hello")
  assert post.save
end

But the test always fails. What is the most likely reason?

medium

A. The database table for posts does not exist or is not migrated.

B. The Post model is missing required validations for title.

C. The test is missing require 'test_helper' at the top.

D. The test method name is incorrect.

Solution

1. Step 1: Analyze why post.save might fail

   If the database table for posts is missing, saving will fail due to no storage.

2. Step 2: Check other options for likelihood

   Missing migrations is a common cause of save failure; missing validations or test_helper usually cause different errors.

3. Final Answer:

   The database table for posts does not exist or is not migrated. -> Option A

4. Quick Check:

   Missing table = save fails [OK]

Hint: Check database migrations if save always fails [OK]

Common Mistakes:

• Assuming missing validations cause save failure
• Ignoring database migration status
• Thinking test_helper absence causes save failure

5. In a Rails app, you want to ensure that every time a new user is created, a welcome email is sent. How can testing help you confirm this behavior reliably?

hard

A. Write a test that creates a user and checks if the welcome email was enqueued or sent.

B. Manually check the email inbox after creating a user in development.

C. Trust that Rails sends emails without testing.

D. Add a print statement in the mailer method and watch console output.

Solution

1. Step 1: Understand the goal of testing email sending

   Tests should automatically verify that the welcome email is triggered when a user is created.

2. Step 2: Identify the reliable testing approach

   Writing a test that creates a user and asserts the email was enqueued or sent is the correct automated way.

3. Final Answer:

   Write a test that creates a user and checks if the welcome email was enqueued or sent. -> Option A

4. Quick Check:

   Automated email test = reliable confirmation [OK]

Hint: Test email sending by asserting mail delivery in tests [OK]

Common Mistakes:

• Relying on manual inbox checks
• Assuming Rails sends emails without verification
• Using print statements instead of tests