You can use https://github.com/swagger-api/swagger-parser to convert a swagger doc into a set of Java objects. Ideally, there should be functionality to create request definitions from them.

Stressor takes a definition and brute forces each field to find at what point it breaks.

eg, if the Stressor was looking a string field, it would run through all the symbols and add characters to the string until the error message changes or it reaches some predefined limit

See DefinitionsTest. There needs to be a better way.

Currently the required message can be set, but all the others are hardcoded

Move messageName and fieldType (which is only used for messages) into MessageConfiguration

Something like trying to do sql injection on string fields? Attacking common weak points?

It only checks the types within the array

It only checks the types of its fields

Ensure only a list of acceptable DateTime patterns are accepted.

Improve how scenarios are created (eg, call out what is under test in addition to value being used) which would result in better ArrayField tests