Notes from 2018 Day 2: Legacy

with thanks to Nicholas Dunning

How to start testing old, monolithic systems

Data output, pruning and mining the results to reduce overhead which leads to a loss of history

Testing frameworks

Introducing code coverage

Dealing with low confidence and flakey tests

Who is responsible when the tests brake

Strategy for small teams working on a single product