BUG? JSONPath Match works differently between SoapUI open software version and SoapUI NG (Ready!API)
Hi,
We started with SoapUI open software version 5.2.1 and are now moving to SoapUI NG (Ready!API) 1.6.0. Suddenly, our testcases began to fail. We then found that the JSONPath Match works differently between SoapUI open software version and SoapUI NG (Ready!API).
Given the following response:
{"errors": [{
"code": "100",
"message": "Message for 100",
},
{
"code": "200",
"message": "Message for 200",
}
]}
The "JSONPath Match" assertion used to work on SoapUI open software version is as below
Expression: $..errors[0].code
Expected result: 100
This assertion fails on SoapUI NG (Ready!API). To pass on the NG version, the assertion has to be rewritten as below (note the highlighted square bracket):
Expression: $..errors[0].code
Expected result: [100]
Could anyone take a look and see if this is a bug? Thanks.
The problem is that we use both version cross different environments (some use open software version and some use NG version), as such that it requires the same test cases working on both environments.
Regards.