ReadyAPI Feature Requests

Would be nice to have the branch name visible in the workspace, so you always directly know in what branch you are working. This decreases the chance of doing things in the wrong branch. ... View more

Hi Team, I have created a utility which will validate the saved response with new response for an api request how to achieve that 1) I will save the sample response which will be compared with response received at run time 2) The utility will generate all the json path for the new response generated and old saved response and store as list 3)it will iterate over any one list extract the content of each node by doing getstring(jsonpath) function and compare with node value received for saved response using same  getstring(jsonpath)  4)it will validate the size if response with respect to saved response by asserting size of both the list 5)if user wants to ignore specfic jsonpath they can pass keyword as exclude it will that jsonpath and will not compare that path value   if integrated with soapui/ready api feature it will save significant time in asserting response  ... View more

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

Currently, assertions for "API Connection" test steps can only be created in the test step itself. It would be better if the assertion test steps could be used for this. However, when selecting the test step to be tested, the "API Connection" test steps of the test case are not displayed. ... View more

Currently, gRPC cannot be updated and cannot be re-imported. This means that all API definitions must first be deleted and then the new API definition must be re-imported.   Test cases that use the deleted and re-imported gRPC API will lose their test steps. ... View more

It would be nice to add a new feature "beautify" json body like in Postman ... 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

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 JIRA integration simplifies the creation of JIRA items (bugs, tasks, etc.)   The JIRA integration now supports attaching a ReadyAPI project file or a log file (see picture below).    It's quite difficult to add any other information from ReadyAPI, since the JIRA dialogue is a blocking pop up window.   I would appreciate an option to attach the test step or test case report, including the request, response, and assertions results.   As a tester, I would like to: execute a test step, test case or testsuite once the test is finished, click the JIRA button  check include test report and create JIRA item The JIRA item would contain the test report in text format.   ... View more

If 'Filter By:' is selected to list FAIL only: When I open one, I would like to move thru the failures only when using the next/previous button. When I have an item highlighted in the list and uncheck filter, selected item stay selected and 'visible'. This would help to see previous and following steps executed. ... View more

The Motivation The Smart assertions are pretty handy as they allow different rules to be set up. There is an option to assign a label, e.g., "Pet tag is present." by right-click on Assertion and selecting "Rename."   The proposal Can you please also add the label in the assertion editor (create or edit assertion) so we can set the label straight away when creating the assertion?   ... 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

Convert response time in milliseconds to seconds format in ReadyAPI ... 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

The need When I import OpenAPI specification into ReadyAPI a new API is created.  When I open the Service Viewer, there are two tabs: endpoints with the service URL specification with a tree of OpenAPI elements and relevant OpenAPI JSON   What I am completely missing is any visual aid to browse the OpenAPI specification, i.e. the UI which Swagger-UI tool provides. I am especially missing a function to browse complex JSON objects.   Proposal Can you please add another tab with a user-friendly visual viewer of the OpenAPI specification? The Swagger-UI functionality would work well.     ... View more

Current situation Currently there's no validation available for JSON messages in REST requests. The only thing to do with JSON is to format it:     For SOAP requests the validation works pretty well: - it validates if the XML is well formed - it validates XML against WSDL/XSD        The need For instance, I have a REST POST request with a large JSON document. I need to validate if: the document is a well formed JSON the document conforms to the API specification (OpenAPI) Can you please add this function, at least for JSON as the most commonly used format in REST?   I would suggest also a check and warning for invisible characters and encoding within the request -- if they come into the request e.g. by copy-pasting, it's very difficult to realize what's wrong. In such cases other tools may work fine (e.g. curl) having the same HTTP headers but still ReadyAPI request fails.   Best regards, Karel   ... 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

Smart Assertions can change Case Sensitive & Active for ALL Smart Assertion Tests at ONCE. Make the CONDITIONS have this same ability - e.g. Change All Assertions to "Exist" or Change All Assertions to "Does Not Exist", etc...  see screen mock up Mock Up: UPDATE ALL CONDITIONS ... View more