when we build a vsi from our swagger file, all the paths from the swagger file end up creating vsi transaction url patterns that end with a trailing '/', even tho the swagger file definition does not.
this causes all the attempts to test to fail, as the pattern cannot be found.
adding a / to the server:port/path/?parm=value&parm=value
allows it to work
OR edit the model url pattern to remove the trailing '/'
this also occurs on the Virtual API Cloud with the same swagger file
is this a bug, or is there something in the swagger spec that make the code do this?
(how to help my users over the hump)