Why testing is integral to Rails - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Rails encourage testing by default?

Rails comes with built-in testing tools and generates test files automatically. Why is this approach important?

A It only helps when using third-party gems, not for your own code.

B It makes the app run faster in production by skipping tests.

C It helps developers catch bugs early and maintain code quality as the app grows.

D It forces developers to write more code without any real benefit.

💡 Hint

Think about how testing affects catching errors before users see them.

Rails encourages testing to help developers find and fix bugs early, making the app more reliable and easier to maintain.

❓ component_behavior

intermediate

What happens when a failing test is run in Rails?

Consider a Rails model test that expects a validation but the validation is missing. What will the test output show?

Ruby on Rails

class UserTest < ActiveSupport::TestCase
  test "should not save user without email" do
    user = User.new
    assert_not user.save
  end
end

A The test fails and shows an error message explaining the failure.

B The test passes silently without any output.

C The Rails server crashes immediately.

D The test is skipped automatically.

💡 Hint

What does a failing test usually do in any testing framework?

When a test fails, Rails shows a clear message so developers know what went wrong.

❓ state_output

advanced

What is the output of this Rails controller test?

Given this test code, what will be the output status code when the test runs?

Ruby on Rails

class ArticlesControllerTest < ActionDispatch::IntegrationTest
  test "should get index" do
    get articles_url
    assert_response :success
  end
end

A 302

B 404

C 500

D 200

💡 Hint

What does :success mean in HTTP status codes?

The :success symbol corresponds to HTTP status code 200, meaning the request was successful.

📝 Syntax

advanced

Identify the syntax error in this Rails test snippet

Which option contains a syntax error that will cause the test suite to fail loading?

Ruby on Rails

test "validates presence of name" do
  user = User.new(name: nil)
  assert_not user.valid?
end

A

test "validates presence of name" do
  user = User.new(name: nil)
  assert_not user.valid?
end

B

test validates presence of name do
  user = User.new(name: nil)
  assert_not user.valid?
end

C

test "validates presence of name" do
  user = User.new(name: nil)
  assert_not user.valid?

D

test "validates presence of name" do
  user = User.new(name: nil)
  assert user.valid?
end

💡 Hint

Look carefully at how the test method is called and its string argument.

Option B is missing quotes around the test name, causing a syntax error.

🔧 Debug

expert

Why does this Rails test raise a NoMethodError?

This test tries to check a model method but raises NoMethodError. What is the likely cause?

Ruby on Rails

class ProductTest < ActiveSupport::TestCase
  test "calculates discounted price" do
    product = Product.new(price: 100)
    assert_equal 90, product.discounted_price
  end
end

A The Product model does not have a method named discounted_price defined.

B The test syntax is incorrect and causes the error.

C The price attribute is missing from the Product model.

D The assert_equal arguments are reversed causing the error.

💡 Hint

NoMethodError means calling a method that does not exist on the object.

If the method discounted_price is not defined in the Product model, calling it raises NoMethodError.