Interesting read and a very clever idea to minimize test cases.<p>I&#x27;ve been doing similar property based testing on some math&#x2F;physics heavy code, with a somewhat similar idea but without minimization. I have test cases that take a number of floating point arguments in range 0..1, which are generated from a 64 bit integer &quot;seed&quot; value picked from a special sequence that is ordered to produce failures as early as possible (failures are usually at 0, 1 or 1&#x2F;2). Any failure can be reproduced by re-running the test case with the same seed value.<p>In my case, minimization doesn&#x27;t make sense since each test case takes a certain number of floats as input. I use about a minute of CPU time per test case (running with 8M different seeds).<p>Example test case (it&#x27;s about orbital mechanics): <a href="https:&#x2F;&#x2F;github.com&#x2F;rikusalminen&#x2F;twobody&#x2F;blob&#x2F;master&#x2F;test&#x2F;twobody&#x2F;eccentric_anomaly_test.c" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rikusalminen&#x2F;twobody&#x2F;blob&#x2F;master&#x2F;test&#x2F;two...</a>