Avoiding Sneaky Testing Antipatterns

on YouTube ↗06m

" summary

Practical rules for tightening Rails test suites: prefer positive assertions like expect(user.save).to be true instead of negations, force a failing test by stashing a bug fix before writing the test, avoid broad RSpec let usage and keep setup inline to preserve cause and effect, and never add production code paths gated by test mode — use gem helpers such as Clearance’s test helpers and FactoryBot for fixtures. Goal: expressive, isolated, reliable tests that actually catch regressions.

AI-written summary · about

" related talks

• 31mGoing on a Testing Anti-Pattern SafariAja Hammerly · MountainWest RubyConf 2013
• 29mCommon Mistakes that make test cases flaky and how to avoid themMaheshwari Ramu · RubyConf India 2023
• 20mApplying RSpec Best PracticesKevin McKelvin · Rubyfuza 2013
• 29m"Testing. Why so serious?"Viacheslav Shvetsov · RubyC 2017
• 44mHow to Stop Hating your Test SuiteJustin Searls · RubyConf 2015
• 46mBetter code through boring(er) testsBetsy Haibel · RedDotRubyConf 2017
• 34mBetter Code Through Boring(er) TestsBetsy Haibel · RubyConf 2016
• 01h 00mTesting HeresiesFrancis Hwang · RubyConf 2008