-
Notifications
You must be signed in to change notification settings - Fork 118
Improve quality of string output #17
Comments
I think making the chance of getting an empty string configurable is desirable. The character distribution is tricky; ideally we'd want to test characters of all UTF-8 encoding forms; that's why it is how it is. I agree spaces would be desirable. As far as duplicates-- right now there's just a small chance (5% IIRC) of it outputting a blank string. That's on purpose, since presumably there's a lot of different places to store these strings, and we eventually want to try a blank in all of them. |
I agree the distribution is tricky, all UTF-8 is desirable. I just think it can be done much better, perhaps interleaving different sources for randomness. Using a wikipedia article as a source, as well as other texts in addition to pure UTF8 could be useful. I've outputted strings from As for blank strings and dealing with duplicates. I think ideally each instance of Just brainstorming, I think it would be desirable to configure the presence of empty stings (I generally like them), but also the guaranteed presence of special strings like More variance on string length as well would be appreciated. |
I ran a sample from
|
Great lib by the way. I'm doing all my testing with gofuzz |
So using the following inside a loop
outputs the following to the console
This does not appear to be a good random distribution of characters. Also empty strings are outputted more than once, so duplicates are not being addressed. Ideally this library has a consistent random distribution of characters, no duplicates, and interleaved white space (also absent).
The text was updated successfully, but these errors were encountered: