Felder71
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
How to get ReadyAPI Maven runner to detect new login license?
Our workplace has officially moved over to the new licenses that you have to login to authenticate with. I've had no problems using it with the ReadyAPI GUI but when I try to run automation through Java on the command line using the Maven runner, it doesn't detect my license. What needs to be done to allow the Java and Maven to see that I am a licensed user? Thanks for your help.88Views0likes0CommentsRe: Two versions of ReadyAPI on the same machine with one license
Hi Chris, Okay, I see my problem now. When using a new version, I created a separate workspace so I could keep everything individualized but the details about the license are specifically in there. So instead, I copied the workspace data from my 3.10.2 folder to my 3.45 folder, cleaned the basic things like logs, preferences, etc. and then opened 3.45 and had no problems with the license. Thanks for the insight!351Views0likes0CommentsTwo versions of ReadyAPI on the same machine with one license
I am running ReadyAPI 3.10.2 on my Intel Mac OS 12.6.5 and want to start migrating our projects to ReadyAPI 3.45. However, I need the ability to be able to run both versions on my system with the license enabled. However, ReadyAPI 3.45 doesn't see the file license I have for ReadyAPI 3.10.2 and if I uninstall the license and install it in ReadyAPI 3.45 then 3.10.2 doesn't work. And I can't activate the license twice, even on my same machine. How can I run both ReadyAPI 3.10.2 and 3.45 with a file based license at the same time? Thanks for your help.Solved431Views0likes2CommentsRe: ReadyAPI 3.0.0 - The closing of projects takes a very, very long time
I appreciate the info. It's really frustrating and I'd think they would be able to figure out what it is churning on. The one thing that has definitely helped is breaking things down into smaller projects, but that has really wreaked havoc with Git. Oh well. Thanks!2.1KViews0likes0CommentsRe: ReadyAPI 3.0.0 - The closing of projects takes a very, very long time
Did anything ever come of this? I have the same issue with my projects in ReadyAPI 3.0/3.1. It's actually a little interesting because with Ready API 2.x, they took a little bit to open but in 3.0/3.1, they open fast enough. But closing in 3.0/3.1 could take forever (if it actually works - sometimes it just crashes) and it was very quick in 2.x.2.1KViews0likes2CommentsRe: SoapUI Pro to SoapUI NG migration - afterLoadScript vs. beforeRunScript
Correct, you have to go in and manually edit it. Additionally, when testing from the UI, you used to be able to rerun the script by going to the Setup script and pressing the Play button. Since the afterLoadScript doesn't appear there any more, you actually have to reload the project itself, which is an annoyance.3.8KViews0likes1CommentSoapUI Pro to SoapUI NG migration - afterLoadScript vs. beforeRunScript
We are in the process of upgrading from SoapUI Pro 5.1.2 to SoapUI NG Pro (Ready! API 1.4.1) and have come upon a key difference in how the project setup scripts work. In SoapUIPro, the setup script for the Project was saved as an "afterLoadScript". This means that the script was run only after the project was loaded. However, in SoapUI NG Pro, the setup scripts entered for the project are saved as a "beforeRunScript". That means that the script is run each and every time before you run the project and not when the project is loaded. This has created a few issues for us. One, when opening the projects originally in SoapUI NG, the setup script appeared to be missing. It did not appear in the UI. When we added it again, we could see it but now it is in the project XML twice, once as an afterLoadScript and once as a beforeRunScript. So if we want to keep it as an afterLoadScript, we have to manually edit the XML since this script tag does not appear in the UI, that I have found. Two, beforeRunScripts are causing issues with our implementation with the Maven plugin. We currently have SoapUI properties in the POM files for Maven that will overlay on each project after loading. This works properly using the afterLoadScript property, because the script loads the default properties and then Maven overwrites the specific environmental ones as necessary. However, this does not work with the beforeRunScript property, because the Maven will overwrite the specific properties and then the load script gets run again right before execution, meaning the necessary properties have been changed. Is there any way to continue to use afterLoadScripts within the UI or are we now going to be forced to manage them within the XML directly? Or will there be an update to the Ready API plugin to put the properties into place after the beforeRunScript has been executed? Thanks, AdamSolved3.9KViews1like6Comments