Episode 33

Back in the Testing Weeds with Sam Phippen and Justin Searls


March 28th, 2018

41 mins 27 secs

Your Host
Special Guests

About this Episode

Back in the Testing Weeds with Sam Phippen and Justin Searls

TableXI is now offering training for developers and products teams! For more info, email workshops@tablexi.com.

Get your FREE career growth strategy information and techniques!

Rails 5 Test Prescriptions is updated, available, and shipping!



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.


02:32 - Dealing with Longer and Longer Test Suites

09:43 - What causes people to get into this trouble?

12:46 - If you had a fast test suite, would you still parallelize it in the CI?

15:12 - What does it mean for your library to still be functional?

21:35 - Bugs found via the dont-break style of testing

24:06 - Inferring which tests are run from a production code diff

29:31 - Coverage, what's it good for?

33:53 - What kind of features would you expect out of a CI-aware testing suite?

Related Episodes

Part I: Episode 004: In The Testing Weeds

Episode Comments