'Invalid syntax! One or more than one opened or closed curly bracket is missing in expression '${${listparam}[0]'.
Please check the configuration file of the executed test!'
When such a 'bracket match' test is already implemented and available, I would expect that this test is applied to every expression.
Addition
Last example without quotes:
"param" : ${${listparam}[0]
causes:
'Invalid nested parameter format: ${${listparam}[0] - The double quotes are missing!!!'
But in my opinion the quotes are not really relevant here - and not missing necessarily. The error handling should give more focus on an '${' that has no matching '}'.
The JSON code
results in
'Invalid parameter format in line: ...
The same with
and with
and with
Yes, the parameter format is invalid - because of a closing curly bracket is missing.
But I wonder why this is not detected. Every '
${
' requires a corresponding '}
'. It's a simple counting of strings.In other expressions this works fine already:
results in
When such a 'bracket match' test is already implemented and available, I would expect that this test is applied to every expression.
Addition
Last example without quotes:
"param" : ${${listparam}[0]
causes:
'Invalid nested parameter format: ${${listparam}[0] - The double quotes are missing!!!'
But in my opinion the quotes are not really relevant here - and not missing necessarily. The error handling should give more focus on an '
${
' that has no matching '}
'.