test-check

mattly 2017-07-04T21:15:31.983266Z

so just as a testament to the power of property-based testing:

mattly 2017-07-04T21:16:17.989504Z

the harness I have for testing calculations & queries against the data warehouse I manage an application front-end for just caught a super-rare edge case

mattly 2017-07-04T21:16:24.990477Z

doesn't actually happen against production data

mattly 2017-07-04T21:16:37.992104Z

but it could

mattly 2017-07-04T21:17:13.996842Z

my test suite started running monday morning, and test.check generated this edge case, and cranked on it for over 30 hours, approx 200k iterations, until it isolated the problem

mattly 2017-07-04T21:17:31.999551Z

and I look at it and go, oh, of course!

mattly 2017-07-04T21:17:53.002593Z

and it was like one of these little 2 character fixes

mattly 2017-07-04T21:18:19.006432Z

but had the problem occurred against production data, nobody ever would have known

mattly 2017-07-04T21:18:22.006900Z

so, thanks

❤️ 2
2017-07-04T21:25:40.065201Z

> doesn't actually happen against production data > but had the problem occurred against production data, nobody ever would have known So how do you know it didn't?