Skip to content

Comment on Optimizing Rails Tests at Doctolib Scale – On Rails

Comments

Florent's team realized their test suite wasn’t just slowing down developers...it was draining focus, momentum, and budget. The root cause? Decisions that quietly piled up over time. Too many factories. Skipped Rails defaults. A bloated CI setup.

So they hit pause, revisited the basics, and started stripping away what wasn’t helping.

This is a case study in technical maturity. A story of how slowing down just enough can help a fast-moving team go further. Worth sharing with your peers.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.