You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An order like that would simplify setting the property values "at class level", "for all classes" in the same syntax" ($propertyName could be tries, seed, etc):
jqwik.property.$propertyName.$className.$methodName=$value -- method-specific value
jqwik.property.$propertyName.$className=$value -- for all methods in class
jqwik.property.$propertyName=$value -- default for all classes
Then the users could override property configuration from the command line (e.g. to ensure CI uses RANDOM seeds for a specific set of properties), users could configure CI jobs with different test durations
I'm not sure there's a need to support "fetch default values from something like jqwik.defaultProperty.properyName=$value" yet.
For instance, I could easily imagine that users might want to have an example property with a single iteration, so asking jqwik to "use random seeds for ALL the properties" looks awkward to me.
Testing Problem
"set property duration from a command line" (see #336)
"override a specific seed with RANDOM when running in CI" (see #149)
Suggested Solution
Support properties like
jqwik.property.$className.$methodName.$propertyName=$value
(a special value would likely be needed for reverting the value to DEFAULT)An alternative syntax could be:
jqwik.property.$propertyName.$className.$methodName=$value
An order like that would simplify setting the property values "at class level", "for all classes" in the same syntax" (
$propertyName
could betries
,seed
, etc):jqwik.property.$propertyName.$className.$methodName=$value
-- method-specific valuejqwik.property.$propertyName.$className=$value
-- for all methods in classjqwik.property.$propertyName=$value
-- default for all classesThen the users could override property configuration from the command line (e.g. to ensure CI uses RANDOM seeds for a specific set of properties), users could configure CI jobs with different test durations
I'm not sure there's a need to support "fetch default values from something like
jqwik.defaultProperty.properyName=$value
" yet.For instance, I could easily imagine that users might want to have an example property with a single iteration, so asking jqwik to "use random seeds for ALL the properties" looks awkward to me.
Discussion
The following issues seem relevant: #145, #149
The text was updated successfully, but these errors were encountered: