ReadyAPI Feature Requests

Hi, it would be nice if Data Sources can be used for the whole project. Right now it is limited to the test case level. ... View more

On writing my code in Groovy I've noticed that the intellisence doesn't always have all the authorised objects/classes/... in it. e.g. I wanted to catch a node difference and tell the script that it needed to add a particular string when not found. On autocompletion of the intellisence the "is AllWhiteSpace" was not present.  I had that in version 2.6.0 and also now in version 2.7.0.  It would be great if Groovy script handles a lot more like C# intellisence.     ... View more

It would be beneficial to be able to abort an entire test execution gracefully through groovy.   In my case I have an async operation that I kick off, delay a small period, check the status then iterate around that for a defined number of retries before deeming it a pass/fail.   In certain cases it does not make sense for me to continue the test suite/entire test run in certain circumstances and I'd like to be able to issue an abort through groovy in this situation.   Hopefully feature request gains traction with community. Thanks in advance. Ken. ... View more

In SoapUI 4.x, the navigation pane used to rememer it's last saved width between sessions.  However, Ready! API does not remember this type of sizing information--every time you restart the app, the pans are back to their default sizes.   Please enhance Ready! API so that all of the panes and view windows remember their last sizes.  Everything is resizable, but it's a waste of time to have to keep manually re-sizing things because the application doesn't remember the settings. ... View more

Provide an option to also list the Test Steps within each Test Case in the JUnit report. Or provide a way to drill down on each Test Case if needed, by default it can still only show Test Case results. This will be greatly benefit for reporting under a Continuous Integration system. ... View more

AFAIK for SoapUI versions up to 1.8.0, the calltestcase step only supports calling test cases within the same project.   We have hundreds of utility test cases in a large project with ~1000 application level test cases that use them.  We also have another project containing tests that need to call the same utility test cases.  Currently we have to maintain two copies of the utility test cases because the second project cannot call into the first.   Instead, we would like to have one SoapUI project containing the utility test cases, and multiple other projects containing the application level test cases that call into the utility tests.  Then we would not need multiple copies of the utility test cases, which is a maintenance headache.   So we'd like to request a SoapUI enhancement to support calling test cases in other projects.  That would reduce our maintenance efforts considerably. ... View more

Currently it is easy using the OTB to parameterize a REST APIs template/query/matrix/header parameter values to dynamically build a URI. However there is no OTB functionality that allows the user to parameterize the parameter values themselves. Im currently working on a project where the REST APIs query parameter names are actually database table column names. Any table attribute in the database is queryable so it would help a lot if there was OTB functionality to enable this. Cheers ... View more

For now there is no possible way to stop a groovy script from executing. If you create an infinite loop for example the application will crash in no time giving you no other option but to stop ReadyApi and start it all over again.   This happened to me a few times and it's pretty annoying. ... View more

How to identify the mismatch in the code implementation with swaggerhub design document ... View more

It would be nice to have a way to enable and disable certain headers in requests. ... View more

Requesting for an enhancement to repeat the every HTTP/REST request for n times with specified delay between each trials until it passes its assertions.   We are facing a problem in our testing while using two web interfaces.  The first REST send a request to second HTTP/REST service which will take some time (Not sure, it may be from 60secs to 300secs anywhere). With a hard coded delay, it was very tough and wasting lot of time for testing.   With this feature, it saves lot of time and effort. I knew this can be done through conditional step, but it has so much work involved with each step.   BTW, basic behavior of any HTT/REST request should not change by default. it should behave like as usual now. One more this is, it is test step level feature. ... View more

I ran into an issue after following this article to place sqljdbc_auth.dll into my <ReadyAPI>/bin to allow for windows authorization on my JDBC requests.   This works great until ReadyAPI updates, this file is not copied over to the new directory e.g. ReadyAPI-2.6.0 to ReadyAPI-2.7.0. The fact that my project depends on this file and I can't included it with the rest of my project files means that there will always be confusion whenever there is an upgrade.   Please either have ReadyAPI automatically copy this .dll to the new directory when there is an update or allow users to maintain this file as part of their project ... View more

Currently there's no functionality that provides the abiltiy to map an XML rest response with repeating elements to a datasink without mapping each indivitual repeating element.   Example: https://community.smartbear.com/t5/SoapUI-Pro/How-to-map-repeating-elements-from-xml-response-to-datasink/m-p/199559#M45747   Is there a way to map a repeating element from a response into a datasink automatically, rather than having to click getData and manually clicking each one.   So, if I have 25 repeating elements. Widgets again. They all have the same attributes. A1, A2, A3. I want my sink to collect each of the attributes from each of the widgets, but I don't want to have to map it explicitly in the data sink property and the every one of the 25 widgets (x3 attributes) in my response.   example:  <widgets> <widget> <att1>abc</att1> <att2>xyz</att2> <att3>asd</att3> </widget> <widget> <att1>abc</att1> <att2>xyz</att2> <att3>asd</att3> </widget> ... </widgets>   In my datasink, I'd like to map these out 1 element to 1 row in excel:  excel row 1 (first widget): att1: abc, att2: xyz, att1: asd  excel row 2 (second widget): att2: abc, att2: xyz, att1: asd    What I'm trying to avoid is this:    All the way through dozens of these objects. ... View more

Currently in ReadyAPI 3.0, it is allowed to create a new Jira ticket but it is not possible to link to a test case. It would be helpful to attach a JIra ticket/tickets to a failed test case. Jira ticket could be of any type(bug, enhancement, task etc.) Clicking on that linked JIra ticket, it will open in Atlassian. Regards, Neena ... View more

If I walk up to a workstation that has Ready!API up, I can't readily tell if a test package, suite, case, or step is in the middle of running, let alone which one is running.  If something is executing, it should be glaringly obvious on the screen no matter which other item somebody has selected to look at, and it should be easy to tell what is running, and where it is in its sequence.   I'm using Ready!API 1.8.0 ... View more

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

Currently in ReadyAPI, the asserted values are not displayed. You have to actually open the assertion (double click on the assertion) to view the asserted value(s). This is somewhat cumbersome, as a tester you want to see all assertions and asserted values in the same overview.     ... View more

The following feature requests seem too small to have their own feature request, so i decided to collect them in a single post.   Enable ctrl+w to close open teststeps, testcases, suites etc. This is standard in a lot of programs now. Tabs in browsers as an obvious example Rename "remove" to "delete" when right clicking a test case (It seems delete is commonly used term in Ready! API). It's delete for the test steps for example. Remember size of navigators after restart.  When in split view, in this case a test step on the left and a test case on the right. Double-clicking a test step within the opened test case editor should open the test step as a tab next to the test case and not in a new third and maximized window. This seems undesirable. Cloning a lot of test steps to another test case, results in a lot of work removing "Copy of " from the name. Renaming while cloning should only happen if the destination has a test step with the same name. Regards Michael ... View more

We currently have around a dozen composite projects, which all use the same set of API. The reason we use so much projects instead of a single big one is for performance reasons. When an API change (adding a new method, adding a parameter, etc) we thus have to update the API of each of the projects manually. We currently work around that by using symlinks, but this solution is clunky at best.   To prevent that, we would like some way to "share" the API definitions between multiple projects, having the API described in a single place and useable by all other projects.   The choosen solution should be compatible with version-control systems (e.g. something we can submit / check out), so any employee with a fresh computer can simply check-out the project(s) and start working without any extra configuration. ... View more