Contributions
SwaggerHub import into ReadyAPI with base domain shared between APIs
We recently updated our SwaggerHub to have a base domain that is shared between our APIs, once we made this change and tried to update/refactor (even tried re-importing) we are unable to import our swagger specs. We have tried download them as well rather than using the URL and we get the same errors. If we try to update/refactor we see this: Failed to update the interface: [ groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object The current character read is '<' with an int value of 60 Unable to determine the current character, it is not a string, number, array, or object line number 1 index number 0 <!doctype html> ^ ] If we try to import we see this very helpful error message:414Views0likes0CommentsReadyAPI hangs upon test case execution
We have a really simple test case, we do a POST call with a payload, get an ID back from the post, then we do a GET request step using that ID after being transferred. Lately, the GET has been responding in almost not time (not a change) but the test case keeps "running". We have our tests run automatically using Jenkins on a schedule, and when that run hits this step, it thinks it runs for 10 minutes, (even though we have the response) which aborts the run. And the rest of the test suite doesn't get run. Disabling this specific test case, lets the suite run to completion, re-enabling and the test case keeps running. The assertions all pass, the response comes back, all within 3 seconds. I tried looking for something similar in the community, but couldn't find anything. Any troubleshooting steps/ideas would be helpful.325Views0likes0CommentsUpdated to 3.40 then 3.40.1 - Lost my coverage capabilities that I had in 3.30.0
We use the project coverage/coverage feature a lot, to verify against the swagger hub swagger specs from our dev team. I am able to use this feature in 3.30.0, but recently updated to 3.40.0 and subsequently 3.40.1. The coverage feature no longer works in 3.40.1. In 3.30.0: In 3.40.1: We do use swaggerhub for our swagger specs, and I have tried refactoring/updating in various forms to see if that may help, but I am stuck with that. Any ideas on how to fix?323Views0likes0Comments