Ruby on Rails
FactoryBot is more than a replacement for fixtures. Advanced patterns—traits, transient attributes, build strategies, and lifecycle callbacks—let you create precisely the objects your tests need without duplicating setup logic or hitting the database unnecessarily. Most Rails developers learn enough FactoryBot to define a basic factory and move on.
Ruby on Rails
RSpec shared examples and shared contexts eliminate massive test duplication when multiple models or controllers share the same behavior. This post covers advanced patterns including custom matchers, metadata tagging, and composable shared contexts that scale across large Rails codebases. Test suites grow fast. A Rails app with a dozen models,
Ruby on Rails
Rails request specs are the right tool for testing APIs—they exercise the full stack from routing through serialization without a real browser. This post covers JSON assertion patterns, authentication header strategies, API versioning in tests, and shared helpers that keep API specs readable and maintainable. Rails provides three layers
Ruby on Rails
Capybara system tests exercise your Rails app through a real browser, catching integration bugs that unit and controller tests miss entirely. This post covers driver selection (Selenium vs Cuprite), async JavaScript patterns, screenshot-on-failure setup, and scoping techniques for complex UIs. System tests are the most expensive tests to
Test Automation
Sidekiq is the standard background job processor for Ruby on Rails. Testing Sidekiq workers well requires understanding three modes: fake (in-memory queue, no Redis), inline (synchronous execution), and real (full Redis-backed queue). Each mode serves a different testing layer. Setup # Gemfile gem 'sidekiq' gem 'sidekiq-
Ruby on Rails
Background jobs are a core part of most Rails applications — email delivery, image processing, webhook dispatch, data export.