🛠 This patch fixes issue #2229, where Numpy arrays of unsized strings
would only ever have strings of size one due to an interaction between
our generation logic and Numpy's allocation strategy.
🛠 This patch fixes a rare internal error in strategies for a list of
unique items sampled from a short non-unique sequence (issue #2247).
The bug was discovered via hypothesis-jsonschema.
🚀 This release improves the error message when "@settings" tries to
inherit settings from a "parent" argument that isn't a "settings"
🚀 This release improves Hypothesis's "Falsifying example" output, by
💥 breaking output across multiple lines where necessary, and by removing
✅ irrelevant information from the stateful testing output.
👕 This patch adds flake8-comprehensions to our linter suite. There is
no user-visible change - expect perhaps via some strange
microbenchmarks - but certain parts of the code now have a clear and
💅 more consistent style.
🚀 This release fixes some cases where we might previously have failed to
✅ run the validation logic for some strategies. As a result tests which
✅ would previously have been silently testing significantly less than
they should may now start to raise "InvalidArgument" now that these
errors are caught.
🚀 This release significantly improves the data distribution in rule
✅ based stateful testing <stateful_testing>, by using a technique called
✅ Swarm Testing (Groce, Alex, et al. "Swarm testing." Proceedings of the
✅ 2012 International Symposium on Software Testing and Analysis. ACM,
✅ 2012.) to select which rules are run in any given test case. This
should allow it to find many issues that it would previously have
✅ This change is likely to be especially beneficial for stateful tests
with large numbers of rules.
🚀 This release adds some heuristics to test case generation that try to
✅ ensure that test cases generated early on will be relatively small.
🛠 This fixes a bug introduced in Hypothesis 4.42.0 which would cause
✅ occasional "too_slow" failures on some tests.
🚀 This release revokes the deprecation of "find", as we've now rebuilt
🚧 it on top of "@given", which means it has minimal maintenance burden
👍 and we're happy to support it.