438: Writing abstractions in tests

What It Covers

Joelle and Steph explore when and how to use abstractions in test code, comparing helper methods, custom matchers, and shared examples for better test readability.

Key Questions Answered

• •Test abstractions: Good test abstractions shouldn't require jumping to definitions - readers should understand functionality from method names like "login_as_admin" without checking implementation details.
• •Custom matchers over shared examples: Custom matchers provide better composition than shared examples, which couple behaviors like inheritance and force unwanted dependencies between test cases.
• •Helper method design: Helper methods should return values rather than set state, be called inline within test examples, and have descriptive names indicating setup conditions.
• •Abstraction frequency: Test abstractions that require frequent changes indicate poor abstraction choices - stable abstractions suggest you've correctly identified truly similar rather than coincidentally similar code.