Paul Holser

@aaron868 Thanks for your interest in junit-quickcheck! Sorry for the late reply. It's up to individual generators to decide when configuration annotations to admit. You can find these as methods...

@aaron868 Sure thing. Any OGNL expression that evaluates to `boolean` is allowed. `#_` is taken to be the annotated parameter. I'll add a couple more examples of the usage of...

@bjordan2010 Thanks for this ... will investigate.

@bjordan2010 I should mention also that if you want to guarantee that the generated values fall within the range you want, you can mark the parameter with `@InRange`: ```java @Property...

@bjordan2010 `@When(satisfies = "#_ > 1000 && #_ < 100000") int i` will have junit-quickcheck generate a random `int`, then subject it to the "when" expression...if it matches, junit-quickcheck verifies...

@bjordan2010 Correct. I wonder if `@Assuming` would be a more evocative name for `@When` ... it kind of behaves like JUnit assumptions, with the idea of trying values until `trials`...

@visi Thanks for this. If doable, sounds like a nice addition.

@visi I'm looking into an implementation for this issue. Suppose the target type is: ```java class Foo { int a; String b; boolean c; } ``` If asked to shrink...

@moifort Thanks for this -- sorry for the late reply. I think this could be a worthwhile enhancement. When the `JUnitQuickcheck` runner executes a test class, it runs both `@Property`...

@moifort What if, instead of injecting random data into `@Before` methods, we provided access to an object of type `Generators`, just like generator classes have? Maybe you could then say...