When to use approval testing? A: Legacy code / hard-to-test new code. 1) For a lump of code that can't divide up to write unit tests. 2) Convenient for small projects. 3) Fantastic for large number of input parameters.
Note: If a podcast uses dynamic ads, the clip start time may not stay accurate.
Ben and Matt trick another live human being into joining them on the podcast. Clare Macrae [claremacrae.co.uk] joins to talk about her work with approval testing, her experiences dealing with legacy Fortran and C++ code, and an upcoming Webinar she's doing on refactoring-to-testability using CLion.