ReadyAPI Feature Requests

For the Smart Assertion tool to be useful, it must be possible to update current values without losing what is already configured. Currently if a piece of data changes, you have to reload the whole response, which causes the loss of all the previous configuration. Moreover, this makes cloning completely useless because if we clone a test, the configured Smart Assertion doesn't work anymore. You need to reload everything. When you have a lot of elements in your JSON response, and you assert the values against a data source, it's a lot of wasting time redoing what you have already done previously. ... View more

Rather than relying on outside tools like jsoneditoronline, having the ability to compare expected response from current response would be very beneficial.  A user must take the time to copy the expected and the current responses into jsoneditoronline to understand the differences when we have responses that are quite large.    Add a new button to the JSONPath Match Assertion dialog to allow for direct comparison in the tool. (side by side view)   ... View more

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

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

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

We use Fiddler to record web traffic and from there we are re-creating the requests in ReadyAPI. Ideally, Fiddler .saz recordings could be imported to ReadyAPI and create the requests from the recording. ... View more

Currently, SAML is not supported for REST services/APIs in ReadyAPI and is only supported for SOAP services. It would be beneficial to have this support for REST/API's as well as SOAP. ... View more

When working on a composite project that has oAuth Auth. it comes to changes to the settings file (new tokens) while developing tests locally. So there is always a unwanted change to this file. Wouldn't it be nice if there is a separate file for just the data that can change in case of new token retrieval? The following can change (as far as I saw): accessToken; accessTokenIssuedTime; refreshToken I would add the separate file than to the git ignore, so that there is no change related to this anymore. It might be also an option to just store the tokens temporary?  ... View more

Hi,   I believe there should be a feature that uses the Swagger definitions for REST API services much more profoundly. The current "Swagger Compliance Assertion" is not covering this. It's too broad and generic. I would love to have an option to automatically create the standard edge test cases based upon swagger definitions as that would save a lot of time for readyAPI customers. There is a security JSON boundary scan, but that only verifies that there is no sensitive data in the response. It doesn't doe anything with the provided swagger information. There is also no way to see what exactly the boundary scan does, except for going into the transaction log to see each individual request payload (https://support.smartbear.com/readyapi/docs/security/scans/types/boundary-json.html)   Suggestion: Button to "Create negative tests from Swagger": - Example1:  Automatically a test cases is created with a REST test step where JSON payload or request parameter is set to whatever minLength / maxLength is defined in the swagger. If for instance maxLength is 99 I want ReadyAPI to have a value set to 100 character length. Expected outcome would then be an HTTP400 (customizable with a predefined response payload check).  - Example2: Automatically test cases are created where we omit the "required" fields (be that headers, request payload parameters or query parameters). So either it's set to null or it is completely missing from the request. Again expectation would be an HTTP400 or HTTP401/403 for authorization headers.     ... 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

Currently there are Assertions to check for Swagger or Schema compliance for REST API. Please consider adding an assertion for checking RODL (RemObjects Definition Language) compliance. ... View more

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

in version 3.9.0 there is a smartAssertion created that deprecates the HTTP assertions. As all of my testcases (a huge amount) have this assertion I'm not going to adapt them manually as this will take a huge effort to do so. No clue why Smartbear has deleted this assertion as I think quasi all of the testers are using this!? Please, re-install the HTTP assertions! ... View more

Hi,   Jenkins plugin which is currently available is having basic features but we need more commands like creating virtual services etc.   Best Regards, Venkata Yedida ... 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