I certainly wouldn't be opposed to having a little bit of fuzz testing incorporated into regular tests as a trial. My only concern is that may be too short and unlikely to find any bugs. But we could always have it run only on CI in the future. It seems like we could also possibly request a VM from INFRA to run fuzz testing full time if it ends up being particularly valuable. https://reference.apache.org/pmc/vms
-- Michael Mior [email protected] Le mer. 12 sept. 2018 à 07:46, Vladimir Sitnikov < [email protected]> a écrit : > Michael>I wouldn't expect this to execute as part of the normal test suite > > Note: we can include limited fuzzing in the regular test suite. > For instance: a single Travis job that performs fuzz-only tests for a > couple of minutes. > That would not increase test duration, however it could eventually find a > gem. > > We can even include a 5 second fuzzer into the regular suite, and it might > dig 1000-10'000 cases or so provided we don't start PostgreSQL there. > > Michael>Either way, it sounds like this > Michael> could be a good contribution if it's so adept at finding bugs :) > > Well, I even have a JIRA for that, however it takes time to add javadoc :) > > Here's one more case where fuzzer would definitely find issues: > https://github.com/apache/calcite/pull/827 > > > Vladimir >
