Hi fsamwel,
I see that you worked with our Support Team. As far as I understand you couldn't reproduce the issue anymore.
Let's mark this question as solved. Please post the update if you see the issue again.
> SoapUI Pro v2.8 is really, really, really old
Hi Rich, thanks for your response. I downloaded the update just Today, so think it's not that old. I'm actually using SoapUI Pro in ReadyAPI 2.8.0. Sorry for the confusion.
Hi fsamwel
ok - Im running v2.7.0 (I always wait for a while before upgrading to the latest version) and I've just tried reproducing what I think you've described - but I'm not seeing quote marks being inserted - please see screenshot of a JSONContent Match assertion
The value was generated without quote marks when I hit 'assert' >> 'for content'
I then selected 'from the current' button - but stiill no quote marks.
can you provide a screenshot to explain?
cheers
rich
I've added two screenshots.
In my json response (Outline) I rightclick the mouse on an attribute and select Add Assertion > for Content.
Next the assertion is shown with quotes added to the attribute content.
When clicking Select From Current also the attribute content is added surrounded with double quotes.
I also noticed that when the attribute is not a string, but for example a boolean, the quotes are not added.
regards, Frank
Hi fsamwel
ok - well that looks like a v2.8 change where the implications to the change/improvement hasn't been completely thought out.
I can understand why SmartBear would make this change in some ways - it means the user has an idea of the datatype being used - json has 4 primitive datatypes:
1. text/string,
2. numeric,
3. boolean (true/false)
4. null
Only string/text values are wrapped with quote marks (e.g. "text value" - this includes dates, datetimes btw - as dates/datetimes are not considered numeric) - all the other datatypes don't get wrapped with quote marks.
As I say - it looks like SmartBear may have introduced this change so the user knows what 'type' the data is - but this then causes your assertion to fail because the 'value' doesn't include quote marks.
This needs a tech support call (see link) cos I'd say this change has introduced a defect that's gonna get old pretty quick unless the other functionality is updated to support the change (like when you hit the 'Test' button)
Best answer I've got for now unless SmartBear can sort this out? I'd download v2.7 - it doesn't display this behaviour.
Cheers,
rich
Hi fsamwel,
I see that you worked with our Support Team. As far as I understand you couldn't reproduce the issue anymore.
Let's mark this question as solved. Please post the update if you see the issue again.
