Make it SPECtacular
summary
Argues that tiny, concrete changes cut spec-writing time: adopt one-to-one describe names like API::V1::Users::PostsController, use explicit context/setup/subject/assertion four-phase test structure, document the testing stack (factory_bot, capybara, custom matchers, odd DB collation notes) and reuse setup with a shared scenario tool — an open‑sourced circumstance gem that loads factory scenarios into specs. Reports that these practices reduce discovery and setup time and make new tests much faster to write and understand.
AI-written summary · about
chapters (4)
related talks
20mApplying RSpec Best Practices
50mWriting Solid Ruby Code
37mSensible Testing
46mBetter code through boring(er) tests
52mStory Driven Development: The Next Generation of Rails Functional Testing
32mMiniTest: Write Awesome Tests
01h 04mClean RSpec: A Workshop on Ruby Testing Craftsmanship
29mHow I Learned to Stop Worrying and Love Unit Testing