The XML Sort tool is somewhat deprecated. It was originally used to sort XML prior to diffing as a means to ignore element order. However, this has been somewhat obsoleted by the fairly recent addition of the XMLUnit diff engine which has a "Ignore element order" option. So, consider not using the XML Sort tool to simplify your test setup.
JSON diffs require array elements to be in the same order, which is why you are seeing this behavior. One way to do this is to convert your JSON to XML using the XML Converter tool, and then use the XML Sort tool to sort the XML before performing an XML diff using the Diff tool. This will require you to use XML within your regression control, which you will need to get by identifying what the sorted XML will look like and then pasting that into your Diff tool.
Is this a bug?
Is this a bug?
SOAtest doesn't have bugs
What version are you currently using?
The feature has been added.
Please try out the updated MongoDB Query Tool from the Parasoft Marketplace.
New online docs have also also been added.
No idea . . . but I'd like to take the opportunity to mention that SOAtest and Virtualize docs are now available on https://docs.parasoft.com/ . Open the SOAtest docs then search for OAuth.
If you are using a REST client, then perfect!
Under the Success Criteria tab, you can put in values like (200, 207, 204) without the parentheses and it will work exactly the way you'd expect. You can also put in ranges like 200-205 and all values in between will be valid as well.
Rename the file from .pvn to .tst. Can't say if this will always work in the future but for now that should work.
@MichaelG I reproduced the issue on my end and found out that IBM has refactored it's driver class. When connecting the data source is looking for a legacy driver that isn't there any more. There is another way though!! (sans restart) Select "Custom" for the driver class and fill out the Driver class, URL, etc.. information. (Pictured)