ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #ruby
Deciding on a mocking strategy for a growing RSpec suite Our team is standardizing how we isolate collaborators in unit tests, and we keep hitting the same unresolved decision: when to use allow , when to use expect , and when spies are the better fit. The suite mixes all three styles inconsistently, and reviewers disagree on what each test is actually promi
I'm getting an error message that I can't find the solution for when I'm trying to install Rails v 6.1.1 on my new Mac machine (still on Catalina, not Big Sur) I have rbenv and Homebrew installed and have updated to the latest version of Ruby (3.0.0). When I put out which ruby I get: /usr/local/opt/ruby/bin/ruby Here's the error code I'm seeing in terminal w
Transactional Isolation and Example Retries Maintaining test isolation typically involves wrapping RSpec examples in database transactions using around(:each) hooks or integration tools like DatabaseCleaner. This ensures that writes are rolled back after each example to prevent state leakage. When integrating external retry mechanisms—such as the rspec-retry
Integration Boundary: Ruby Application and Third-Party REST APIs When testing Ruby integrations using the VCR and WebMock libraries, the primary goal is to simulate external API behavior without relying on live production credentials or risking the exposure of sensitive keys in version control. While VCR allows for the recording of real interactions into YAM
Ruby's generational garbage collector uses specific thresholds to determine when to trigger a Minor GC versus a full Major GC. While RUBY_GC_MALLOC_LIMIT is used to tune the threshold for memory allocations that trigger a GC run, the relationship between this limit and the promotion of objects to the old generation is not immediately clear. In a high-allocat
Goal: Identify a reliable way to detect when a Ruby connection pool is approaching exhaustion before threads experience timeout‑induced latency spikes. Constraints: The connection_pool gem only raises a Timeout::Error after the per‑checkout timeout expires and does not emit warnings or metrics; developers must either poll pool.available_size or rescue except
rspec