Controller tests in Ruby on Rails - Performance & Optimization

Performance: Controller tests

MEDIUM IMPACT

Controller tests impact development speed and test suite runtime, affecting how quickly developers get feedback.

Testing controller actions with many database calls and full rendering

Ruby on Rails

test "index action returns success" do
  get :index, params: { format: :json }
  assert_response :success
  assert_includes @response.content_type, 'application/json'
end

Avoids full view rendering and reduces database calls by testing JSON response only.

📈 Performance Gainreduces test runtime by 70%, faster feedback

Testing controller actions with many database calls and full rendering

Ruby on Rails

test "index action" do
  get :index
  assert_response :success
  assert_not_nil assigns(:items)
  assert_select 'div.item', minimum: 1
end

This test triggers full view rendering and multiple database queries, slowing down test execution.

📉 Performance Costblocks test suite for 100+ ms per test, slows feedback loop

Performance Comparison

Pattern	Database Queries	View Rendering	Test Runtime	Verdict
Full controller test with view rendering	Multiple queries	Full rendering	Slow (100+ ms)	[X] Bad
Controller test with JSON response and mocks	Minimal queries	No rendering	Fast (30 ms)	[OK] Good

Rendering Pipeline

Controller tests run outside the browser but simulate HTTP requests and responses, triggering database queries and view rendering if not optimized.

→Database Query

→View Rendering

→Test Execution

⚠️ BottleneckView Rendering and Database Query during tests

Optimization Tips

1Avoid full view rendering in controller tests to reduce runtime.

2Mock or stub database calls to speed up tests.

3Focus controller tests on response status and logic, not on detailed view content.

Performance Quiz - 3 Questions

What is a common cause of slow controller tests in Rails?

A Mocking database calls

B Using JSON responses only

C Rendering full views and making many database queries

D Testing only response status

DevTools: Test profiler or Rails logs

How to check: Run tests with verbose logging or use a test profiler gem to see database queries and rendering time per test.

What to look for: Look for tests with many queries or long rendering times causing slow test suite execution.