Ruby Midwest · November 2011
Test Your Legacy Rails Code
Everybody wants to do test-driven development, but switching to TDD or BDD on an existing project that doesn't have tests presents special challenges. Often, the current code is a tangled mess of dependencies that defeats the very concept of unit testing. Worse, if somebody has attempted TDD in the past, you might have a test suite that needs to be fixed before any new tests can be written.
"This conference... at one point in the talk you can hear Jim Weirich being the only person to laugh a joke. This is also the conference where Bob Martin started his end-of-day-one keynote by correcting mistakes from earlier speakers, including myself. The organizers gave me Martin's note card from the talk, but I lost it."
Tags
Related Talks
RSpec: It's Not Actually Magic
RailsConf 2015
Testing Best Practices, or the Five Habits of Highly Effective Tests
RailsConf 2012
Testing Should Be Fun
RubyConf 2012
Test Doubles Are Not To Be Mocked
RubyConf 2016
High Cost Tests and High Value Tests
RubyConf 2017
Related Posts
-
How To Manage Duplicate Test Setup, or Can I Interest You In Weird RSpec?
Dec 2023
-
Testing Strategies
Jun 2021
-
20 Years
Mar 2021
-
The Entropy Essays #2: Why Did You Hire This Test
Jun 2020
-
The Entropy Essays (XP 2020) #1: Test speed
May 2020