ReadyAPI Feature Requests

Smart Assertions are very useful when having lots of data that need to be asserted.  However currently there are a few issues that make it more difficult then it needs to be:    1. No Search Facility that allows quickly to jump to an item.  2. No conditional flow where assertions can be managed depending on some response details. 3. No facility to deal with lists that are unsorted and can be in a different order each time. 4. No facility to convert the Smart Assertions to Groovy Script which would make it useful as a tool to get a basic script with all the assertions that can be further edited to deal with special cases.   Our responses contain hundreds of pieces of data that need to be evaluated. The Smart Assertions are great for quickly generating the assertions of a response but since we have many lists which don't arrive in a specific order, this does not work very well for us.  If the Smart Assertions could recognise lists and pre-order them before assertion this would solve this problem and save us a lot of time.     We also have an issue with repeated properties like for example version numbers that we only want to change once and then have it used in many places.  However using a property only works as long as the data doesn't change.  When data changes and we have to make a "Load from Transaction" again, those properties have to be added again.  It would be nice to have something like an "Update from Transaction" that notices changes but doesn't overwrite existing items that haven't changed and preserves the properties being used.  A differential dialog might be useful here when updating where we can see the changes, modify them if necessary or have them applied.   Another great feature would be a conversion from Smart Asserts to Script.  Other test applications that we use for desktop applications already can do this and it would be nice if SmartAPI also would be able to generate a script from the Assertions.  This would help with situations where we need to have lots of special flows , loops and transformations of data but don't want to always have to write each assert from scratch.       ... View more

Reference Issue - https://community.smartbear.com/t5/ReadyAPI-Questions/Ready-API-3-42-0-automatically-updates-projectVersion-every-time/m-p/240988/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExBSklETVhHWkdEMTUxfDI0MDk4OHxTVUJTQ1JJUFRJT05TfGhL#M57307   projectVersion value changes everytime a project is saved. When trying to Pull changes from git, setting.xml needs to be committed first, but it re-appears again as a new change, which blocks pulling from git.  The "Discard all changes", don't really discard the document. ... View more

Current situation ReadyAPI DataGenerator provides different random values (random integer, email, name, city, etc.) I like this function since it creates nice test data. However, the random values are only accessible via DataGenerator DataSource.   Proposal It would be great if we could use them in: REST, SOAP, and other requests Variable setup Groovy scripts etc. In ReadyAPI the random values could be available via: expansion e.g. ${#Random#FirstName} Get data function adding a Random category in the top level Implementation proposal Wrapping Java Faker (https://github.com/DiUS/java-faker ) would do the task.   Java faker can be configured to use localized data (e.g. english names, spanish names, etc.) The faker provides a lot of interesting data useful for testing, just to name few of them:   Address Animal App Artist Avatar Aviation Book Business Company Color File Finance Food Name Nation Number PhoneNumber and many more, including some funny categories like ChuckNorris.   ... View more

In Ready API, we can import API definition directly from SwaggerHub. When in a new version is available, I can't use the update definition feature to load the openAPi specs from Swaggerhub. ... View more

The need In ReadyAPI there are nice options of reporting, however there is missing any function to do report post-processing. The post-processing needs are: to send a report via email put the report into a storage create a Jira item etc. Currently the report files are just placed in the output directory.   On TestCase and TestSuite level there are Report script holders, but the purpose of the script is to   extend the reporting options   (it is executed before the reports are finished, not after), i.e. for report pre-processing. On the project level there is no such option.   Solution proposal A good place to execute specific actions are   the events. But there is no "ReportListener.afterReport" event.  Please add a new event ReportListener.afterReport which will be triggered after any report is finished by testrunner.  Such event will be used by Groovy scripts to do the report post-processing.   ... View more

List of Smart Assertion Conditions 0.  <, > , >= , <= 1. Equals                AND   Not Equal 3. Equals (one of)  AND   Not Equal (one of) 5. Exists                 AND       Does NOT Exist 7. Empty                AND   NOT Empty 9. Contains            AND  does NOT Contain 11.  Matches (regex)  AND.... AND..... (!!)  And...  and..... and....!!!     Uh..... what happened to NOT MATCHES (regex)  ?!?! ... View more

It would really be helpful if OAuth2 authentication would be enabled for  Kafka topics just like for Rest APIs. Tokens would be dynamically  generated and then put a reference to it into the connection settings.    This feature would enable automating Kafka topics using OAuth2 as tokens expire after a given period (60 minutes or less usually)   ... View more

Currently, when you insert a URL (for example) that contains a "-" (e.g. https://mycompany.com/core/reg/by-binary-data) the shown text after saving the test is struckthrough.  The Test Details/Step text box is hard-coded to only use the Wiki-style Renderer and so characters that are perfectly valid in URLs are interpreted as some manner of markup. Just allowing customers to modify the renderer used to the Text Renderer in these fields, like the other JIRA text fields on forms, would allow these characters to be shown as expected. ... View more

I'm sorry, but to me the idea mentioned Intellisense-on-custom-groovy-library by @runzTH almost 6 years ago (wow!) is still not implemented, even though labeled as such. In current version ReadyAPI 3.10.0 I still do not have the kind of intellisense I would like to see:    - no hassling with .jar files, I want to have interoperability with all of the groovy files in my custom script library like defined in the ReadyAPI project. A restart of some sort I can understand, but when we need to start with importing files we know this is something that will only work locally and for that version.  - PLEASE: Proper IDE capabilities, like auto-complete, auto-formatting, code error detections (missing curly bracket for instance),  renaming/refactoring,  search (and replace),... in ALL scripts (setup scripts, groovy tests steps, tear downs, script library,...). It is such a breeze when I use other (front-end) test automation tools to see that I can do those things, but then return to ReadyAPI and feel like an IT-guy from the 90's.  - I'd like proper javaDoc documentations to know what each method does. Currently I can only see what parameter type(s) I need to provide, but not what this method actually does or what I can expect to be returned.   Scripting is such an extra weapon to be used in ReadyAPI, it's a shame it cannot be made more powerful by Smartbear. ... View more

Allow to copy current value from Smart Assertion. Sometimes need to change one value in Smart Assertion and don't want to set/change all values from response. So please allow to copy current value from Smart Assertions. ... View more

It would be very helpful to have the option to ONLY populate FAILED assertions from received data in the Smart Assertion. Now it's only possible to populate all data, which results in losing, for example, valid values asserted by property data. ... View more

Can SmartBear add a linter to ReadyAPI? I would like to make ReadyAPI check the quality of a user's work (test cases and scripts), i.e. perform linting. The work can be checked as the user is typing it or when the user requests for it. For example, ReadyAPI should complain when the user does not write a description for a test case, the user's groovy code has known bad practices etc. Some rules can be ignored by the user, but some should be mandatory. I'd also like to generate a report of all the issues in a test case/script to see if people ignored the complains and did not follow best practices. Keywords - Linting, Linter, Code Analysis.   PS - I asked this as a question also over here https://community.smartbear.com/t5/API-Functional-Security-Testing/Linting-or-automatic-code-checking-in-ReadyAPI/m-p/208439#M47532   ... View more

Hi,  There is no possibility currently to integrate ReadyAPI and Zephyr Squad on JIRA Server.  In this documentation, it is mentioned that only Zephyr Squad Cloud is supported.  It would be nice to have it for Zephyr Squad on Jira Server ... View more

When Smart Assertion is created property is used for some values in Valid Value column in Smart Assertion (ReadyAPI v3.9.2). Some values might changed in response so it is nice to use "Populate from Received Data". But it changes all values from response. It would be nice that there would be possibility to save/leave not changed properties. ... View more

I would like the ability to mask passwords in the settings.xml file for Composite Project files. Our security team flag this as risk since usernames and passwords are exposed in this file. We would like to continue to use the Auth Repository feature while keeping our project files in Composite format. ... View more

Current behaviour: 1) In the additional request headers tab of a SOAP/REST test step I select multiple headers (the selected headers visually are selected by having the color blue = OK).  2) I click on the delete bin button. 3) Only the first header is deleted. Expected behaviour: ALL of the selected headers should be deleted. If a use wants to delete 10 headers he now has to manually select them and delete them one-by-one. This is frustrating.   Note: this issue has been around for ages.  Additionally: We (luckily) can select and copy the headers properly by doing a select and then Ctrl+C. The feature of copy-pasting request headers might not be really visible in the UI (e.g. there is no "copy" button), but I am very grateful this is possible through Ctrl+C. Might be wise to visually allow this to? ... View more

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.      ... View more

It would really be helpful if OAuth2 authentication would be enabled for soap-Requesrts just like for Rest APIs. Our application supports this and other clients also. For ReadyAPI we use at the moment BasicAuth as workaround ... View more

There must be a feature by which i can re-order my Test Steps or Test Cases or Test Suites at once, right now i am able to re-order one by one and it takes lot of time if i have huge number of test-cases. ... View more