CBTF vs Elasticsearch

CBTF throws deliberately problematic inputs at exported functions and reports which ones error, warn, or survive. It now covers 85 input classes, fuzzes multiple named arguments per call, runs in parallel with a per-function timeout, and reports results as a classed object with print, summary, length, and whitelist methods for pruning false positives. Output control has been refined repeatedly — the latest release adds grouping by input or by function and a summary-only mode.

The package has moved from a script-shaped tool to a test-suite component. The single-argument, sequential fuzz() of the early releases could not finish a large namespace or survive a function that simply hangs; the mirai rewrite fixed both, and multi-argument support widened what a run can actually reach. Nearly everything since has gone into making results triageable rather than merely produced: whitelisting, result classes, grouping, and terminal output that fits real function signatures. Note that the 0.1.0 through 0.3.0 entries carry backfilled timestamps recorded in reverse order within under a minute, so their published dates do not reflect release order.

The steady expansion of the input catalogue from 70 to 85 with a new time class suggests more input classes are the cheapest next win; the reporting surface is now detailed enough that machine-readable output for CI would be the natural follow-on.