Last time, we saw how deleting stuff from a test case can be an easy and fun route to the root cause of a bug. It’s less easy and less fun when the test cases get big. The inner loop of test-case reduction can get old quickly: delete stuff, run the special command, check the output to decide whether to backtrack or proceed. It’s rote, mechanical, and annoyingly error prone. Let’s make the computer
![Automated Test-Case Reduction](https://cdn-ak-scissors.b.st-hatena.com/image/square/2256f3638315333b7d505c2dd3cbb1ee56b00102/height=288;version=1;width=512/https%3A%2F%2Fwww.cs.cornell.edu%2F~asampson%2Fmedia%2Ficon%2Ffavicon512.png)