Contributions
Re: [BUG/Limitation]: Use wildcard in JSONPath expression Expected Result not working?
OH... another question or limitation. I just tested for JSONPath Match Assertion, if I use "*" on a single property that does not even exist, the test still passes.... how can I assert a dynamic property is some sort of number or at least not null? Picture attached, I want to make sure the matching nested object has a number property called id and it can not be null. Its value is auto-generated so it is dynamic.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes2CommentsRe: [BUG/Limitation]: Use wildcard in JSONPath expression Expected Result not working?
Thank you Richie for the help. Unfortunately, I can't use SmartAssert as the assertion should only happen on the nested object that meets my condition. So it is dynamic and the sequence is not guaranteed. So my case is the endpoint could return an array of X objects, during the X there should be 1 object that has a "boardwalkDeposit" property, which I will need to assert that it has a id, sequenceNumber and amount etc. Since "id" is generated, so I have to use wildcard on it to check it is not null. Ideally, I should check id is some sort of number but I don't think ReadyApi can do that in JSONPath expected results. I guess what I can do is creating multiple JSONpath check steps for each of the properties under "boardwalkDeposit" object. Personally, I do believe this issue should be concerned as BUG or limitation of ReadyAPI that should be highlighted in their documentation.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes3Comments[BUG/Limitation]: Use wildcard in JSONPath expression Expected Result not working?
Hi there, As shown in the picture, I want to check one property of my selected nested JSON object is a number. It can be any number just not null, so I would like to use wildcard in the JSONPath Match Assertion. However, it still tries to assert "*" as a character. I'm on ReadyAPI 3.20.0. Wondering is this a bug?1.7KViews0likes5Comments