ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #rspec
Learn how RSpec's aggregate_failures block groups multiple expectations into one failure report, reducing reruns and keeping specs focused on a single logical condition.
RSpec's aggregate_failures lets multiple expectations run to completion and reports all failures together, eliminating the fix-one-re-run cycle for related assertions. Here's how to use it, a concrete controller spec example, and when to avoid over-aggregation.
Extract repeated RSpec assertions into shared examples, but watch for hidden dependencies on let and subject.
Learn when to use RSpec's lazy let versus eager let! for test state management. Includes comparison table, concrete example, and performance trade-offs.
RSpec stops at the first failing expectation by default. aggregate_failures lets you collect multiple related expectation failures per example without aborting early.
let is lazy and memoized per example; let! adds a before hook. How the mechanism works, where it bites, and a two-minute check to verify it in your suite.
Stop duplicating tests for common interfaces. Learn how to use RSpec shared_examples to define behavioral contracts once and enforce them across multiple classes.
Learn how to use RSpec's let and let! helpers to manage test dependencies, avoid state leakage, and optimize test suite performance through memoization.
Learn how to define RSpec shared examples once and reuse them across classes that implement the same interface, with parameterization, file organization, and debugging tips.
ruby