Summary

In this chapter, we looked at tools we can use to diagnose a failing test. We can print values to the console using the Ruby p method or the Awesome Print gem. If we’re having trouble isolating when a breaking change was introduced, we can use git bisect to isolate which change caused the problem. If we think we have a test failure caused by the interaction of multiple specs, rspec bisect or minitest bisect is our friend. If we want to walk through our code step by step, the Pry gem offers a number of tools to help us do exactly that.