downgrade to lower ready api version 3.40.1 from latest Hi, I want to downgrade to version 3.40.1 for my project work, where can I download it from? I currently have latest ready api 3.58.0 license.

I am looking for a *fair* comparison between rest assured and ready api for rest api testing only. I am *not* interested in looking at the unrelated features which ready api has that rest assured does not have, i.e. SQL connection, MQ connection, SOAP …

Open groovy script > Right click > Get data > Select the test case step which has the API call > Select request/response etc. def request = context.expand( '${YourAPICallStep#Request}' ) The "request" is type of class java.lang.String.

4- if i rename the "Application" in Projects, the next time when i re-open ready api, the name remains with old name, why? It's a big problem, because when i import another wsdl file in my project, i have two applications with the same name. So during an update, i do not know what soapui is updating. What i expected:

Stop using the older version of Ready API. Ensure all outstanding changes to Ready API projects are committed to our source control. Go through all of our Ready API projects, upgrading them to the new version making sure all the test still pass. Commit all changes from the upgrade to our source control. Start using new version of Ready API.

Hey abomans Have you tried one of the other downloads? I.e. .zip rather than .exe download? On the page youve linked to, there are multiple instances of readyapi! packaged up with various different compression containers.

I found how to set keystore for use by SOAP or REST API calls, but do not see instructions for using cert's for JDBC calls. Some suggestions I found asking to add my app's IP/Username/etc. to the pg_hba.conf file on DB server. Unfortunately, cloud-based DB server does not have that file.

Hi richie . Thanks for your time an good effort! I appreciate this. To answer your questions: 1) I did started with groovy snippets step by step where as I came up to this result.

Review File Content: Open your API definition file in a text editor to check for any syntax errors or issues. Correct any problems found. Use Specific Protocol: Instead of "Determine Automatically," try specifying the protocol explicitly when importing. For example, if your API definition is in OpenAPI format, choose "OpenAPI" as the protocol.

Hey MadhuEP . ReadyAPI! can report malformed .xml project files as invalid when attempting to load . So - just to be absolutely clear - all the projects that were created and maintained on a previous version (do you know what version?) worked immediately before on the previous version and as soon as you upgraded and tried opening the projects, you get the invalid file warning?