Originally posted by soapuser12 on September 21, 2017
Hello there,
We are having issues with the ‘Import Postman Collection’ functionality in SoapUI Pro. After importing the V1 postman collection with no issues, we get a URISyntaxException when executing any of the imported requests. It sort of looks like the application is not properly doing property expansion when it imports the postman collection. For example if you have ‘http://{{host_property}}’ defined in your postman request URL, the app does not do a property expansion substitution as stated in the docs: https://www.soapui.org/docs/postman-collections.html.
We also tried this in SoapUI community edition and ReadyApi version as well. We suspect the same issue, even though we get a different error message. (e.g.SoapUI community edition gives null pointer exception).
Please let us know if there is any work around/solution.
Originally posted by soapuser12 on September 22, 2017
works like a charm boss. I was able to load the jar with the plugin manager on readyAPI and successfully import the postman collection. Thank you.
FYI: i went ahead and tested this with the community version as well, by manually replacing the default postman plugin jar with the one u sent. Result: ‘import from postman’ menu option does not show up.
Originally posted by soapuser12 on September 26, 2017
sorry about that. Thought I accepted it.
one more ReadyApi issue i did notice over the weekend: the import functionality only imports the requests. Which is ok if you are only doing simple collections. However, If you have tests associated with the collection, ReadyAPI tries to create testcases for them, but ends up creating empty testcases. Instead of testcases with respective assertions per the conversion rules.
the previous post before yours was during September last year.
I installed the plugin today into my ReadyAPI! and the version installed was v1.2.0 - rather than what was attached earlier in the post (which was an earlier version).