Enhancement: For error tests, log the value that is used as trigger on a high level in the log.html for quicker debug analyses

Nobody has claimed this yet.

The actual used value that should trigger an error responsecode is currently quite deep hidden on debug loglevel. This makes debuganalyses sometimes pretty hard. And only if de API indeed throws the error message.
If the response does not contain the errormessage it is not clear what value should have triggerd it.

Perhaps it is possible to add this value to the log like:
`Log error trigger value is ${value}`

Even better if the reason or api specs for the specific field are added.
`Log error trigger value is ${value} , accepted value is integer with max length 5`

Start by tracing the error-test flow that produces log.html and locating where the value triggering an error response is available. Review how API field rules are represented before deciding whether to log only the trigger value or also its accepted type and length; done means the generated log exposes the relevant value and error tests verify the output.

Written by the indexing model from the issue text.