I think this is a fairly straightforward bug, when I right click on some json content (sample below with data redacted for privacy) and select 'assert on content' it auto generates a jsonpath assert but immediately throws an 'invalid jsonpath' error. It seems the . in the json element is throwing things off.
Here is the json child element sample (the structure is similar to data/parent/metadata/place.ctry)
The assert being generated is:
But that implies .ctry is a sub element to place, not one element.
Ps. This is from readyApi 1.4.1
Forgot to mention that the simple solution would be to change it to:
Did that manually and it appears to work fine.
Thanks for reporting this behavior. Could you please check if you can reproduce it when using the latest Ready! API maintenance build? Perhaps, it has already been fixed. You can download the build here:
While I understand your question and it is certainly not unreasonable, I am afraid I am not able to do that - we cannot just upgrade readyAPI from a known stable version in our work environment as we need to use it daily. I respectfully suggest forwarding this bug to your maintenance department so they can assess and try to reproduce it? Or is there a more appropriate way for me to submit a bug report than this forum? If so - my apologies and could you let me know what that is? 🙂
You can submit this behavior to our Support Team - http://support.smartbear.com/product-list/
However, as a rule, our R&D Team prepares patches for the latest product version. It’s unlikely that they will create a patch for v. 1.3.
BTW, v.1.3 and v.1.5 can be installed side-by-side on one computer.
Oh - I would not expect a patch for any previous version, with the workaround I found we are fine - I just meant to say that I am not in a position to check if a bug also exists in a later version of the product, I just don't have the time. The link you provided seems to not quite apply? The closest category for ReadyAPI would seem to be 'technical inquiry' which it is not - its purely a bug report? Or is that the right category?
In the previous version of the boards there was a specific forum where bugs could be reported, I've done so a few times - is it an idea to set one up again?
Technical inquiry is the correct category. Our Support Team works closely with our R&D Team to investigate the issue and analyze the possibility to create a patch to fix it. This is the reason of why we recommend submit possible issues to our Support Team.