Ability to parameterize REST API Parameter Names
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
Ability to use windows authorization without copying sqljdbc_auth.dll each time ReadyAPI updates
I ran into an issue after following this article to placesqljdbc_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
Clone Assertions UI needs some love
1) Change the Target Test Case selection from a drop-down single-selection list box to a sub-dialogue that allows multiple Test Cases to be selected and test steps to be selected for each test case. 70% of the time I spend in ReadyAPI is repetitive data entry of cloning assertions one at a time between test cases where the default test case is the one I'm using for the source. 2) Change the default selection of the Assertions from none selected to all selected. No one ever needs none cloned, that's a non-operation.
Share APIs between projects
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.
ServiceV selective routing
The routing option is too limited to be useable today. At my current client we need the option to route certrain ranges to the real back end services, or the option to do so via scripting (return route instead of return template). We have specific ranges of easily identifiable Virtual Customers, those should returnone of ourtemplates while real customers should return the real service response.
Could use more than 5 visible lines of script in ReadyAPI ServiceV right most viewing/editing pane
ReadyAPI ServiceV right hand window viewing/editing pane has a number of script nodes that have a script editing area that is not able to be resized vertically. Only 5 lines of script are visible when it should be able to grow as desired. Start Script, Stop Script, OnRequest Script and AfterRequest Script cannot be grown more that 5 lines. That takes a while to scroll through when those scripts are many lines long.
Masking encrypted properties in ReadyAPI Test for Azure DevOps task instead of plain text
Hi, The latest version of ReadyAPI 3.20.0 seems to fix encrypted properties being displayed as plain text in logs within the ReadyAPI software itself but this does not translate when running the project from Azure DevOps using the "ReadyAPI Test for Azure DevOps task" as encrypted properties are still being exposed there. 1. The project password for the task is in plain text - This property should be masked as anyone who views the task would be able to download and access the encrypted project and its properties. 2. Encrypted properties are displayed in the logs/requests as plain text The password has been encrypted in the custom properties using the "selected properties" project encryption . However, encyrpted properties are being shown in the task logs when a request that uses the properties fail or when logged using groovy script as plain text. This display of encrypted properties as plain text is unacceptable especially when creating production tests so it would be benefical if encyrpted properties are not exposed. Thanks, KayleighGeneral usability improvements to ReadyAPI
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
Run From Here at the Test Case level (not just the test step level)
I distinctly remember being able to use a 'Run From Here' option (context menu when right clicking a test case from the Test Suite summary screen i.e. the one where the bars show green and red when a test passes or fails). It seems to be gone in one of the last versions? I can see inside a Test case if you right mouse click on a test step you can select run from here. What happens to me is I have a suite with 20 cases and case 14 fails. I then inspect it and want to run case 15 onwards so in the past I would right mouse click this test case and choose Run From Here ...Excel datasink to consume repeating xml elements without having to map multiple properties
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.include assertion values in Assertion window
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.Jira Integration - Link an existing Jira ticket to failed test cases
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, NeenaEnhancement to UI to alter Navigator to show testcases with unsaved changes
One feature that would be very useful would be to alter the "look" of a testcase/testsuite in the Navigator showing there are unsaved changes on a testcase/testsuite. Presently there does not appear to be any discernible difference shown to let you know there are unsaved changes in a testcase or testsuite. Unfortunately I have fallen foul of this issue where my machine has lost power prior to me saving and I didn't appreciate how many unsaved changes I had in flight..... and by default the autosave feature isn't enabled. Thank you in advance. Ken.Add password parameter for the loadtestrunner
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, GiovanniSmart Assertion on GraphQL Request Step
I was wondering why we can make a Smart Assertion on REST requests but can't make a Smart Assertion on GraphQL Request Step. We are currently using REST requests to test GraphQL as suggested and since the Smart Assertion tool is crucial in API testing for us but was wondering if there were any plans to support Smart Assertion in GraphQL requests? Seems like functionality of sending a REST request as a graphQL request is much more feature rich at this point in time.Need a Feature to Clone a Test Step to Multiple Target Test Cases
https://community.smartbear.com/t5/SoapUI-Pro/Clone-at-multiple-test-cases/m-p/27262 In reference to the above thread creating an idea to vote it up and get the feature added to SoapUI. Currently, when cloning, only one target TestCase can be selected. If we have the ability to clone a test step to multiple target test cases, user will not have to perform cloning action multiple times.
JSON-Schema supported (E.g.: in WADL-Files)
We specify our JSON-Format-Definition with the JSON-Schema. It would be nice to validate the data directly within SOAP-UI. Schema specification (IETF RFC Draft) http://tools.ietf.org/html/draft-fge-json-schema-validation-00 Understanding JSON-Schema: http://spacetelescope.github.io/understanding-json-schema/ Generating JSON-Schemas: http://jsonschema.net/#/ Validating JSON-Schemas: http://json-schema-validator.herokuapp.com/ Using JUnit Tests rest-assured: http://www.jayway.com/2013/12/10/json-schema-validation-with-rest-assured/
Junit style report not being accurate in Data-Driven tests
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.customizable floating license timeout period
I believe the license manager for ReadyAPI has a default timeout of 12 hours of inactivity to auto check-in a floating license session. It would be really useful if that timeout period could be customizable to any time period the customer desires. Would that be possible to implement as a new feature?Populate automatically the Test Cycle in JIRA with Zephyr Test cases results mapped in ReadyAPI
Once you mapped the test cases in a ReadyAPI project with Test cases in Zephyr and also you create an empty test cycle ReadyAPI should update the empty test cycle with the results (the same way is done in Test Complete)Case #00150388: Assertions using an "OR"
I had entered a ticket and got reffered to the community board for this enhancement request. I've notice since the release of Ready_API 1.4 several GUI memory related issues. Mostly because the current project that I an on required sucha large list on parameters, approximately 150. This has proven to be problematic when creating a datasource with a long list or a simalarly large number of assertions. Having said that, the paarticular issue is as follows. I created approx. 150 test assertion, most of them were simple Match Content, comparing the Datasource Feed, with the output of a JDBC test step. I did this assuming thatthere would always be data, or particulatly formated data coming from the file feeding the datasource. Well when I had a difference from what I was expecting aI had an "Oh S@#$T" moment. Now I have to delete 150 assertions and recreate 150 script assertions. Proposal: Enable the Assertion's "Expected Result" window to accept multiple expect data using logical AND/OR (&&/||) statements (See attachment). I know that there is a similar feature using th eAssertion test step, but its too bulky and wouldn't be worth the effort vs replacing with a script assertion. It also heps the script to me a bit more maintainable as future releases present similar siuations.Make the left view panes remember their hidden/visible settings between sessions
Please make the left navigation panes remember their hidden/visible status between sessions. Most applications remember these types of settings, and it is a shortcoming in Ready! API. This should include settings for all items in the View menu. Currently, none of them remember their settings between sessions. It's more user friendly to have these panes remember this settings. Otherwise, if someone wants View settings that are different from the default, they have to manually re-set them after ever restart of Ready! API. (e.g. The new API Navigation pane--since it uses a lot of space and causes issues with pushing the Properties pane off the screen, so I have to repeatedly manually hide it now).Maximize button for assertion editors, and have the editors remember their sizes
When we went to Ready! API, I had been hoping that the assertion editors would get a re-working. However, they still have all of the same short-comings of SoapUI. Specifically, the editors don't give you very much realestate in their default size when you open them. I always have to drag the editors to give myself more space to work in. To address this, I suggest two improvements: Add a Maximize button on all editor windows that are currently resizalbe (e.g. XPath and XQuery editors, etc.). Have each type of resizable assertion editor remember the last size that it was openned to, so that whenever you open an assertion editor of the same type, it'll open at that size. This should be persistent between sessions, and be by assertion type (NOT specific to individual assertions--far too many of those to keep track of).
JUnit-Style HTML Report - customizable report title via Project custom property
Hello, I would like to customize the title of the JUnit-Style HTML Report which now reads "SoapUI Test Results" with the value of a project-level project property. In my case, I would have a value to indicate the environment name. The idea is when the report is distributed to the interested parties it would answer the question "What environment were the SoapUI web service tests in this project executed? Thank you, DinoImprove mousewheel scrolling (currently very slow) when viewing Project or Test Suite component
When viewing the Test Suites list in the Project component view or the Test Cases in a Test Suite view, one is able to use the mousewheel to scroll up and down in the list. This is great. Except! Except that the scrolling is superbly slow. It takes like...5x longer to get where you want to go than it should. In my humbleman's opinion. It would be supremely #sweet if the mousewheel scrolling was more in line with standard scroll speeds for navigating lists of objects.Does ReadyAPI (SoapUI) support flow chart as a feature in future
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 hereSwagger: use body model when importing
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:Able to modify JUNIT reports to include Request/Response for failed cases
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.Need a Feature to Clone multiple Test Steps to Single/Multiple Test Cases
This idea is about cloning multiple test step at single instance of time to single/multiple test cases. Currently, when cloning, only one Test Step can be selected. If we have the ability to clone multiple test steps to single/ multiple target test cases, we will not have to perform cloning action multiple times. Please upvote this whoever want this to be implemented.Customize default "Test Case options"
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.Adding a name/description to Events
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 easierdifferentiate between each event and its function.
Option to Disable Download of Virt from VirtServer
Hi within the virtserver (from within ServiceV) when you right click on a virt you have the option to 'Download' in doing socreates anew 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 oldversions of avirt 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 thisisn'ta technical issue and more of procedural education issue, this would bea nice to have to discourage people from potentially doing something detrimental and causing confusionAuto start Virt on VirtServer startup
Hi Can we get amechanism 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 startwith 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 MikeAbility to add a "Notes" test step
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!Clear saved history, disable saved history
Ideally, an option where usercould 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.Eliminate the 'Exit ReadyAPI?' prompt on application close
When I close ReadyAPI I'm prompted with a dialog box asking if I really want to exit (see attached screen1.png). I have the Save Projects on Exit option enabled, and I get the exit confirmation prompt whether I've made any changes to projects or not. I request an enhancement where if the Save Projects on Exit option is enabled, the exit confirmation doesn't appear. It makes no sense to continually ask the user to confirm a deliberate action (99% of the time) when there is no danger of losing changes if the Save Projects on Exit option is enabled. If users accidentally close the application when they didn't mean to, they can simply start it back up. Very few other mainstream client applications ask the user to verify whether they want to exit the application. If this is a way to ensure users don't lose unsaved changes, why does the Save Projects on Exit option even exist?
Set auth profile for multiple environments at the same time
Set auth profile for multiple environments at the same time. Within our project we have several environments. Some environments within the same domain. Now we have to set the authorisation profile for each environment seperately this is rather difficult as it requires constant switching between environments. I would like to have the posibility to set all environments in one overview. I have created an example see, the attached image.Make UTF-8 default encoding in ReadyAPI
As of (I think V3.0) the encoding is put on (I asume) ANSI by default, as all groovy scripts are writing ansi textfiles. I don't know about y'all but in Belgium we mostly (understand 90% of the time) use UTF-8 encoding for textfiles as we program in english but with data in different languages. That's why UTF-8 is more aquanted with 'umlaut' characters, ' é - à - è- etc....'. This is unicoding. ANSI is more limited in strange characters. It was so before, why has it changed? I have to think about it on each new update version of ReadyAPI as well as installing the integrations again and changing the performances for logins again..... Propositions: 1) Make sure that each update doesn't mess with the ReadyAPI configuration of the user 2) embed the UTF-8 encoding again in your versions by default. 3) If you really don't want to humor me, then at least after new update of a new version give a warning that this change needs to be done for all the persons who needs to code in UTF-8. Maybe with a link to an explanation page on SmartBear website on how to do so. (adding that line in the Readyapi.vmoptions) Thanks in advanceCustomer facing API for quickly retrieving license details
Hi, I'm managing licenses for my group (around 200 people) and we're using several SmartBear products. The licenses are scattered across 3 different my.smartbear accounts and keeping track of the licenses is pretty cumbersome. Would it be possible for SmartBear to create a small API to quickly retrieve license details. ex.: I'd like to check if a user activated a license or what software licenses are assigned to the user, so instead logging in to 3 different accounts in search for the user, I'd like to make API call to get this info quicker. Cheers, Wacław
ReadyAPI Feature Requests
379 Posts
