Summary: <h2>Back in the Testing Weeds with Sam Phippen and Justin Searls</h2> <p>TableXI is now offering training for developers and products teams! For more info, email <a href="mailto:workshops@tablexi.com" rel="nofollow">workshops@tablexi.com</a>.</p> <p><a href="https://stickynote.game" rel="nofollow">Get your <em>FREE</em> career growth strategy information and techniques!</a> </p> <p><a href="https://pragprog.com/titles/nrtest3" rel="nofollow">Rails 5 Test Prescriptions</a> is updated, available, and shipping!</p> <h2>Guests</h2> <ul> <li> <a href="https://twitter.com/samphippen" rel="nofollow">Sam Phippen</a>: Tech Lead at <a href="https://www.digitalocean.com/" rel="nofollow">DigitalOcean</a> and member of the <a href="https://github.com/rspec" rel="nofollow">RSpec</a> Core Team</li> <li> <a href="https://twitter.com/searls" rel="nofollow">Justin Searls</a>: Co-founder of <a href="http://testdouble.com/" rel="nofollow">Test Double</a> </li> </ul> <h2>Summary</h2> <p>I'm back in the testing weeds with Sam Phippen, lead maintainer for RSpec-Rails, and Justin Searls, co-founder of Test Double and author of testdouble.js. We talk about long-running test suites: are they bad, or just misunderstood? Does parallel CI solve all testing speed problems, or just some of them? Then we move to a wider view, what does it mean to test your library as part of a larger ecosystem. And, how can we leverage coverage or CI information to make for more useful testing tools over the lifetime of a project.</p> <h2>Notes</h2> <p>02:32 - Dealing with Longer and Longer Test Suites</p> <ul> <li><a href="http://confreaks.tv/videos/rubyconf2017-high-cost-tests-and-high-value-tests" rel="nofollow">High Cost Tests and High Value Tests</a></li> </ul> <p>09:43 - What causes people to get into this trouble?</p> <ul> <li><a href="https://youtu.be/Tc5z64XIwIY" rel="nofollow">On Writing Software Well #5: Testing without test damage or excessive isolation</a></li> </ul> <p>12:46 - If you had a fast test suite, would you still parallelize it in the CI?</p> <p>15:12 - What does it mean for your library to still be functional?</p> <ul> <li><a href="https://www.npmjs.com/package/dont-break" rel="nofollow">dont-break</a></li> </ul> <p>21:35 - Bugs found via the dont-break style of testing </p> <ul> <li><a href="https://grpc.io" rel="nofollow">GRPC</a></li> </ul> <p>24:06 - Inferring which tests are run from a production code diff</p> <p>29:31 - Coverage, what's it good for?</p> <ul> <li> <a href="http://rspec.info/" rel="nofollow">RSpec</a> </li> </ul> <p>33:53 - What kind of features would you expect out of a CI-aware testing suite?</p> <h2>Related Episodes</h2> <p><a href="http://www.techdoneright.io/004-testing-with-sam-and-justin" rel="nofollow">Part I: Episode 004: In The Testing Weeds</a></p><p>Special Guests: Justin Searls and Sam Phippen.</p>
