Testing the Multiverse

It’s a basic principle of testing that minimizing dependencies will make you happier, faster, and more productive. But what happens when you can’t? If your code plugs into or extends another gem, comfortable isolation might be out of the question. Stubbing and careful design can carry you a ways, but eventually you need to actually test your code against those gems you’re building on. Luckily, there are ways to reduce this pain. We’ll dig deep on creating a simple environment to check your work against multiple dependencies. We’ll see patterns that help avoid pulling your hair out when those dependencies change. We’ll even search around the raw edges, examining how to verify what your code does when it lands in an environment you haven’t tested. There’s a multitude of gems out there to build on. Let’s see how we can test with them!

Transcript

1. Testing the Multiverse A Story with Issues 1 https://flic.kr/p/dYVeRE @jasonrclark
2. Ruby on Bails 2 ! On! Bales Ruby https://flic.kr/p/a5jhu1
3. 3 2018
6. PIOR 6
7. Programmer Input/ Output Ratio 7 input command length output length
8. Way better than LOC! 8
10. 10 Straw https://flic.kr/p/6dNzso
33. 33 A! B! C
34. Always! Bundle! Constantly 34
61. 61 https://flic.kr/p/pvXudv
68. 68 Crooner https://flic.kr/p/8vVcNf
71. 71 https://flic.kr/p/cfcFx7
84. v 84
95. 95 https://flic.kr/p/a5jhu1 Bundler Rake Versions Parallelize Suites
96. 96 https://flic.kr/p/a5jhu1
97. 97 https://flic.kr/p/ncrk3c
98. 98 https://flic.kr/p/ncrk3c @jasonrclark