Supporting @settings(backend="hypofuzz") would be quite useful - for example, as an easy way to work with Pytest fixtures, or to support fuzzing in environments where Pytest is not available at all (CPython alphas?).
The implementation isn't trivial, since we have to rearrange a lot of code to both fit with the IR-oriented, context-manager-scoped interface for backends - while also having a hook to allow for interleaving execution of multiple tests - but I don't think there are any fundamental difficulties.
This change is independent of #3, but strongly complimentary in practice.
Hypothesis has recently grown a notion of alternative backends, which use the new IR layer (https://github.com/HypothesisWorks/hypothesis/issues/3921) to support e.g. symbolic execution (https://github.com/HypothesisWorks/hypothesis/issues/3914).
Supporting
@settings(backend="hypofuzz")would be quite useful - for example, as an easy way to work with Pytest fixtures, or to support fuzzing in environments where Pytest is not available at all (CPython alphas?).The implementation isn't trivial, since we have to rearrange a lot of code to both fit with the IR-oriented, context-manager-scoped interface for backends - while also having a hook to allow for interleaving execution of multiple tests - but I don't think there are any fundamental difficulties.
This change is independent of #3, but strongly complimentary in practice.