Rickard Nilsson

The prometheus-client (and other deps) version boundaries should probably be defined in the cabal file too, but I made no changes there since I don't know how you want to...

I think the following behaviour makes most sense: The test runner takes the following parameters: propertyTimeout (see #5) minSuccessfulTests maxDiscardRatio (see #11) minTotalDuration (this issue) The test runner will keep...

@2rs2ts Thank you for the detailed analysis of this weird behavior. Would you say your `genBigDecimal` implementation would make a good candidate for `Arbitrary[BigDecimal]`? I think it looks fine, but...

We are slowly moving towards reproducible tests in ScalaCheck by making the generators deterministic. In the end, that should make the stateful tests reproducible too.

@dpolivaev You are correct, even if the tests are deterministic there is nothing that says the system under test is deterministic. So somehow saving the final (minimized) command sequence would...

@alathon This has been discussed before, and it actually was possible to do this in the previous implementation of `Commands`. I'm now convinced that I should try to re-add this...

@alathon A PR is always appreciated :) With a 'clean' version do you mean something that would work with the parallel testing, or a cleaned up version of your existing...

This is a known limitation of ScalaCheck, shrinking will not always respect the generator bounds. You can add a pre-condition to you property with ScalaCheck's implication operator (`==>`) to avoid...

@Kevin-Lee I consider it something that should eventually be fixed, but it might require larger changes in ScalaCheck, and no one is currently working on this.

There's `org.scalacheck.Test.checkProperties` you can use for this. It's possible that it could be better documented.