ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #rspec
Verified Double Contract Enforcement RSpec's instance_double and class_double provide a mechanism to ensure mocks remain synchronized with the actual implementation by verifying method signatures against the underlying class. This prevents tests from passing when the source API has drifted. Dynamic Method Resolution A challenge arises when the target class u
Goal: Determine whether RSpec’s filter_run_when_matching :focus takes precedence over filter_run_excluding :slow when an example is tagged with both :focus and :slow in RSpec 3.12. Constraints: The official documentation does not specify the precedence between these two filter types, and anecdotal reports show inconsistent behavior across different patch lev
RSpec provides distinct mechanisms for verifying method calls on test doubles, specifically through traditional message expectations and the use of spies. While expect().to receive() sets a requirement before the action occurs, spies enable an "act first, assert later" pattern using have_received() . There is a design consideration regarding the internal sta
When using RSpec with WebMock to intercept HTTP requests, the library intercepts calls at the library level. This mechanism typically bypasses the actual SSL/TLS handshake, meaning certificate validation logic is never executed. Developers need to verify how the application handles expired certificates, mismatched hostnames, or untrusted CAs. There is curren
When implementing DRY test suites in RSpec, shared examples can be integrated into a spec using either it_behaves_like or include_examples . While both methods allow for the reuse of common expectations, they handle the execution context and documentation output differently. The primary goal is to determine the optimal method for maintaining clean failure tr
The RSpec timeout feature introduced in version 3.8 allows a global limit to be set for each example, causing a Timeout::Error when exceeded. Currently this limit does not automatically apply to child example groups; each group or example must declare its own timeout metadata to obtain a different limit. This lack of inheritance can lead to inconsistent time
RSpec core does not include a built-in retry mechanism. Retry behavior is commonly added via the rspec-retry gem, which re-runs the entire example and its before and after hooks on each attempt. The integration boundary between rspec-retry and database-backed examples raises a concern about side effects. Because each retry executes the example code again, wr
RSpec's match_message matcher is frequently used to validate error output in request specs, particularly for authentication and authorization failures. When custom error objects are raised by controllers relying on Devise or CanCanCan, the matcher's string-comparison logic may produce inconsistent results depending on error-message formatting, localization,
ruby