ReadyAPI Feature Requests

When importing a swagger file which contains some body model, it would be good if R!API could use it to generate the corresponding REST request.   Basically, let's say I have a swagger "operation" with the following: apis": [ { "path": "/example", "operations": [ { "method": "POST", "nickname": "handlePost", "produces": [ "application/json" ], "consumes": [ "application/json" ], "parameters": [ { "name": "data", "paramType": "body", "type": "InsertionData" } ], And the InsertionData model defined like that:   models": { "InsertionData": { "id": "InsertionData", "properties": { "id": { "type": "integer", "format": "int64", "required": "true" }, "address": { "type": "integer", "format": "int32", "required": "true" } } } }     When I import this using Swagger, R!API will create a blank POST request with an empty body:   I would expect it to create a default body like this to the request instead: ... View more

Right now, JUNIT reports are not modifiable at all. They are important when comes to running test cases via some CI and host result/report at a url. JUNIT reports are so simple and do not give information about the REQEST/RESPONSE  of a failed step to actually look at the reason why the test cases failed on the test server which might run successfully on local. Across various communities, I see that this feature is required by most of the users, a lot of discussion around it, and the way suggested is via maven project which seems to put more effort than writing test cases. ... View more

We use TestRunner (be able to hook up to build system) to execute the test suite and generate JUnit style reports, currently, SoapUI pro doesn't treat each dataSource row as a test case, therefore, if one out of ten dataSource row (test case) fails, it fails the whole test cases, we want this report to accurately show how many really fails and how many really passes in the report Summary page.   Please see the screenshows, one is the Summary page, another one is Drill-Down Faulures page.    I have talked to Jeshtha about this issue.    At Oracle, we have many licenses in our devision alone, the report not being accurate is a BIG issue for the management.  ... View more

Test cases have options assigned to them, which define if the test should abort as soon as a step is on error; if the HTTP session should be maintained; etc. Those options can be found here: http://readyapi.smartbear.com/structure/cases/options/basic   As a developer who writes a lot of tests, I'd like to be able to define the default value of those options once so I don't have to edit each newly created TC.   For example almost all my test cases needs to have the "abort test is an error occurs" option disabled. Having to edit this option manually each time is pretty cumbersome, and easy to forget. ... View more

Hi within the virtserver (from within ServiceV) when you right click on a virt you have the option to 'Download' in doing so creates a new local project   can we have an option to disable this please   the reasoning: We have our project files under source control and we've inadvertently seen old versions of a virt deployed because somebody kept downloading the version from the virtserver as opposed to getting the latest from source control (which was work in progress and hadnt been deployed) whilst I admit this isn't a technical issue and more of procedural education issue, this would be a nice to have to discourage people from potentially doing something detrimental and causing confusion ... View more

Hi   Can we get a mechanism to auto start virts when a VirtServer starts up, if you're using a Large VirtServer at capacity the task of manually starting each applicable virt in turn is going to be somewhat tedious   i.e. a setting within ServiceV alongside or in the general Virt 'Info' section with a checkbox for 'Auto start with VirtServer' then if the flag is set and the virt is deployed if VirtServer is stopped and restarted (sys reboot for example) the Virt would not need human intervention to restart it   an overall view would also be highly beneficial especially if it could also configure the flag whilst deployed i.e. within the VirtServer panel in ServiceV where we can view the active Virts and Metrics etc, a view of all deployed virts and their auto start flags with the ability to switch on/off the flags (in a similar way the rows of data in a datasource can be switched on or off)   regards Mike ... View more

Ideally, an option where user could selectively clear history for specified test case(s) / suite(s) would be nice.     Option to save (or not save) the history could be a checkmark on test case options ... that way you could proactively stop the collection of the history on a test case by test case basis.  ... View more

  The Conditional Goto Test Step functionality is quite restrictive compared with equivalent SoapUI Test Steps such as Property Transfer. This limits how useful the Conditional Goto is and therefore how powerful SoapUI scripts can be without resorting to Groovy. I am not sure how to configure the existing Conditional Goto for response messages containing CDATA, so for us the Conditional Goto is never used.   In my opinion, using Groovy, for a tester without a development background, can be a significant hurdle to overcome.   Please enhance the Conditional Goto functionality to allow source data other than just the previous response message. I suggest a user interface similar to the Property Transfer to allow any message or property to be selected for comparison.   Property Transfer (flexible):   Conditional Goto (very limited):   Thanks.   ... View more

JMS message properties should support the following types besides String.   boolean byte short int long float double     ... View more

Hello, using the table log of loadUI Pro there are two possibilities to save timestamps in log files: unformatted and formated. Unfortunately the default format is not suitable for our needs: - the date is missing - Milliseconds are devided by ":" which cannot be handled by e.g. Excel   It would be nice to have the possibilty to set the time format in the global settings of loadUI (using the standard notation like 'dd.MM.yy hh:mm:ss,000').   Thanks and regards, Christian   ... View more

I have gone through scripts for parallel execution of suites or cases, but couldn't find scripts for parallel execution of projects. The script that i am going to share does the parallel execution of projects. One needs to place it as one of the test steps of a test case of a project. import com.eviware.soapui.model.propertyexpansion.DefaultPropertyExpansionContext def project1=testRunner.testCase.testSuite.project.workspace.projects["Project1 Name"] def project2=testRunner.testCase.testSuite.project.workspace.projects["Project2 Name"] DefaultPropertyExpansionContext con1=new DefaultPropertyExpansionContext(project1) DefaultPropertyExpansionContext con2=new DefaultPropertyExpansionContext(project2) project1.run(con1,true) project2.run(con2,true)   . ... 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

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 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

Anyone met such a situation: you may create a complex test case to process a successive operations against business. and then created many steps / loop / properties transfer / assertions...etc. It's difficult to maintain and it's not easy to quickly undertand what test case is about. If there is a chart to describe the flow and explictly show entire workflow of test cases check then would be better. Any ideas to better construct your test case and make it intuitive. Welcome to show your opinions here ... View more

  Would it be possible to add a name and/or description against an Event. Currently it only states whether it will run after a test case or a test suite. But we are getting to a point were we have multiple events in this list and its becoming harder to quickly understand what each event does. A simple name/description would make it much easier  differentiate between each event and its function. ... View more

I would like to be able to add a test step that just holds text notes.  It wouldn't get executed, it would just be a place to record comments.   Currently, I use a Groovy Script test step and comment everything out.  That works but it would be nice to have a cleaner way.  (I could use the description for a test case, but I never see those descriptions unless I think to go and look for them.)   Thanks!   ... View more

It would be useful to have Test Suite tagging, similar to the Test Case tagging which is already available.   This would be especially useful when using the TestRunner through the command line and being able to supply Test Suite tags. ... View more

When I close ReadyAPI, I'm prompted with a dialog box asking if I really want to edit. This box appears regardless of whether I've made any changes, or if I have the auto-save project option enabled (which I do).   I request that this prompt be removed, or at least be optional via a user preference. It's silly to have to confirm an action I am deliberately taking and an annoyance when using ReadyAPI constantly. Few applications work this way and certainly not ones that can automatically save user changes, which is the main reason you would want a confirmation on exit. If users do it by accident, there is an easy solution: just start ReadyAPI back up. ... View more