Maximilian Algehed
Maximilian Algehed
In situations like this: ``` do var0
We currently expose things like `Actions(..)` and `Step(..)` etc in the public interface of the library. I'd like to limit what we expose to the "intended use-case" to avoid confusion...
Trying to bring things up to date to make sure the issues we've seen in CI on #397 aren't due to old versions.
Right now the only conventient way to control how long a test runs for in QuickCheck is by modifying `maxSuccess` in one way or another. However, this is a bit...
Consider the following: ``` $> quickCheck $ forAllShrink (pure undefined) (\ () -> []) $ \ () -> True *** Failed! (after 1 test): Exception while generating shrink-list: Prelude.undefined CallStack...
This introduces two changes: `initialState :: Gen state` instead of `initialState :: state` and a new callback `setup :: state -> m ()` to `RunModel`. Checklist: - [x] Check source-code...
I'm not 100% sure I like this design, but now you can do `quickCheck $ prop_BlaBla . getMoreActions` to increase the number of actions generated in traces without changing other...
c.f. #415
@nick8325 we are _very_ confused about what's going on here. `mapTotalResult` results in repeated calls to `property` on something of type `Property`. This in turn results in repeated layers of...