Hello, I'm using the latest version from RedayAPI (3.0.0) and my project is password protected - the properties are encrypted. When I want to run functional tests in pipeline, I can give the password over the command-line parameter -p but this parameter doesn't exists for the loadtestrunner. This fact is not an error but a missing function. Without this feature, encoding the properties in a project is a major drawback when you want to automate the load test because I must deactivate the passwort protection to run the loadtestrunner. This is a strong security restriction, especially if you want to protect the passwords/token/secrets used in cloud repositories. A lot of services are provided in the cload nowadays and the trend is increasing, besides the reason I ask the reader to vote for the function to introduce the password parameter for the loadtestrunner as well. Thanks in advance for the votes. Greetings, Giovanni
... View more
I would like to see the following improvements to the LoadUI interface: Feedback on status of agent readyness, i.e. has the agent received/finished initializing test cases. This is would be a really nice feature as it's impossible to figure out when an agent is ready. Sometime it takes a long time for the project to be uploaded to the agent and for the agent to announce "[SceneAgent] The **** scenario was loaded." in the log, other times it never gets ready. Allow drag'n'dropping of agents under Distribution, such that they can be reoganized. Currently they are seamingly sorted by date added. Resizing Agents in the Distribution list such that a better overview can be achieved. This could also be achieved with an option to view the agents as a list, while allowing the same context menu as well as the option to turn agents ON/OFF. Prevent Horisontal scrolling of Agents under Distribution. I currently have 4 agents and the 4th is already outside of view. Floating the agents in the window will allow more agents to be within the view. Enable multiple selection for removal of scenarios from agents. It currently takes 1 right-click and 1 left-click for each scenario. I have 30 scenarios added to each of my 4 agent which would total 120 mouse click to remove all of them. It's easier to remove the agent, add it again and assign scenarios, which isn't really desirable. Better detection of online/offline agents. Example: The remote agent is running and the Agent under distribution is "ON". Close the remote agent, let ReadyAPI detect that it's disconnected and start the remote agent again. ReadyAPI won't detect that it's running. Transfer dependent files to agents. A ReadyAPI project has a "Script Library" property, so copying the contents of this would be a nice addition Also copying the contents of the -Dsoapui.ext.libraries vmoptions folder would be great. Regards Michael
... View more
Now in soapui NG 2016-04-11 14:27:55 response time: 227ms (833 bytes) Feature to be added in SOAP Ui Ng We want the responce as perfect in milli seconds, so that the reponce time will be exact. 2016-04-11 14:27:55:785 response time: 227ms (833 bytes) Vam
... View more
Here you can review submitted feature requests and vote up the ones you like! If you can't find the feature you want - go ahead and suggest your own idea. Ideas with the highest rating can be implemented in the product.