Ruby on Railsframework~8 mins

Integration tests in Ruby on Rails - Performance & Optimization

Choose your learning style9 modes available

Learn Why Deep Visual Try Challenge Project Recall Perf

Performance: Integration tests

MEDIUM IMPACT

Integration tests affect the overall test suite runtime and can impact developer feedback speed during development.

Running integration tests during development

Ruby on Rails

test 'user login flow', :focus do
  post login_path, params: { email: 'user@example.com', password: 'password' }
  assert_redirected_to dashboard_path
end

Uses faster request-level tests without full browser simulation, speeding up test execution.

📈 Performance Gainreduces test runtime from seconds to milliseconds per test

Running integration tests during development

Ruby on Rails

test 'user login flow' do
  visit login_path
  fill_in 'Email', with: 'user@example.com'
  fill_in 'Password', with: 'password'
  click_button 'Log in'
  assert_text 'Welcome'
end

Running full browser-based integration tests on every code change blocks developer workflow due to slow execution.

📉 Performance Costblocks developer feedback for several seconds per test, slowing development

Performance Comparison

Pattern	Test Runtime	Resource Usage	Developer Feedback	Verdict
Full browser integration test	High (seconds per test)	High (browser + DB)	Slow feedback	[X] Bad
Request-level integration test	Low (milliseconds)	Low (DB only)	Fast feedback	[OK] Good

Rendering Pipeline

Integration tests do not affect browser rendering but impact developer productivity by increasing test suite runtime and resource usage.

→Test Execution

→Database Access

→Network Simulation

⚠️ BottleneckTest Execution time due to full-stack simulation and browser interaction

Optimization Tips

1Run full browser integration tests selectively to avoid slowing development.

2Use headless browsers and parallelize tests to improve speed.

3Focus integration tests on critical user flows, use faster request tests elsewhere.

Performance Quiz - 3 Questions

Test your performance knowledge

What is the main performance drawback of running full browser integration tests on every code change?

AThey slow down developer feedback by taking several seconds per test.

BThey cause layout shifts in the browser.

CThey increase bundle size significantly.

DThey reduce database query speed.

DevTools: Test Profiler or CI Test Reports

How to check: Run tests with profiling enabled or check CI logs for slow tests and resource usage.

What to look for: Long test durations and high memory/CPU usage indicate slow integration tests.