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
Use case: I want to generate test data for java.util.jar.Manifest.
Manifest contains Attributes that is Attributes implements Map<Object,Object>.
Technically speaking attribute keys and values are strings, however the restrictions on keys and values are different.
For instance, keys should match [a-zA-z0-9_-]{1,70}, however keys can contain almost everything except newlines.
However I want not just random strings as keys, but I want the generator to produce well-known key names like Manifest-Version.
So far so good, I think behind the lines of implementing AttributesGenerator extends Generator<Attributes>.
Use case: I want to generate test data for
java.util.jar.Manifest
.Manifest
containsAttributes
that isAttributes implements Map<Object,Object>
.Technically speaking attribute keys and values are strings, however the restrictions on keys and values are different.
For instance, keys should match
[a-zA-z0-9_-]{1,70}
, however keys can contain almost everything except newlines.However I want not just random strings as keys, but I want the generator to produce well-known key names like
Manifest-Version
.So far so good, I think behind the lines of implementing
AttributesGenerator extends Generator<Attributes>
.Frankly speaking, I do not like how
gen.make
is instantiated at each and every generation attempt.I wonder if I could "inject"
Generator
instance with constructor or another configuration-like method.For instance:
The text was updated successfully, but these errors were encountered: