Goto Chicago · August 2018
High Cost Tests and High Value Tests (somewhat less Ruby-centric version)
There is a value in writing tests and there is also a cost. The currency is time. The trade-offs are difficult to evaluate because the cost and value are often seen by different people. The writer of the test bears much of the short term cost while long term benefits and cost are borne by the rest of the team. By planning around both the the cost and value of your tests, you’ll improve your tests and your code.
"I got asked on very short notice to give this talk a second time at a more general language conference, so it's less Ruby specific. Fun fact is that the person who went before me talked about error checking on NASA code, tough act to follow."
Tags
Related Talks
Test Your Legacy Rails Code
Ruby Midwest 2011
Testing Best Practices, or the Five Habits of Highly Effective Tests
RailsConf 2012
Testing Should Be Fun
RubyConf 2012
RSpec: It's Not Actually Magic
RailsConf 2015
Test Doubles Are Not To Be Mocked
RubyConf 2016
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