Import Postman Collection - Fails with net.sf.json.SJONExecption: ["requests"] is not a JSONArray
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2021
10:00 AM
11-02-2021
10:00 AM
Import Postman Collection - Fails with net.sf.json.SJONExecption: ["requests"] is not a JSONArray
I have tried to use the 'Import Postman Collection' in SoapUI file menu options and always get the following error.
I have seen a previous post below but this appears to be if you are using the Chrome Postman Plugin, not a client version, so I do not believe that installing ReadyAPI and then installing a ReadyAPI Postman Plugin in it is relevant, and do not want to install it unless necessary. An obvious question is why put an option to Import Postman Collection in the SoapUI GUI if it does not work without some actions being taken to rectify it,
Can anyone confirm if they are using postman (non-Google Plugin version) and successfully imported a collection?
Labels:
- Labels:
-
Integrations
-
Performance Tests
1 REPLY 1
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2021
06:28 AM
11-03-2021
06:28 AM
Hey @PABLOH1,
I have used both imports on SoapUI AND ReadyAPI, however the problem using the imports is that if google change the content (adding keywords, etc.) or formatting of the collections (incrementing the collection versions), then the importer fails until it's been updated to support the new collection content.
SoapUI currently only supports postman collection v1 exports, whereas my current postman version supports exporting collection versions v2 and v2.1, so unless youre using a really old version of postman, the SoapUI import procedure is always going to fail when attempting to import postman at the moment.
Cheers,
Rich
I have used both imports on SoapUI AND ReadyAPI, however the problem using the imports is that if google change the content (adding keywords, etc.) or formatting of the collections (incrementing the collection versions), then the importer fails until it's been updated to support the new collection content.
SoapUI currently only supports postman collection v1 exports, whereas my current postman version supports exporting collection versions v2 and v2.1, so unless youre using a really old version of postman, the SoapUI import procedure is always going to fail when attempting to import postman at the moment.
Cheers,
Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
