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
See more ideas labeled with:
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
See more ideas labeled with:
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
I work from a laptop with 2 extra screens and am having issues with Ready showing (up) correctly. - Ready on the main screens works correct - Ready on a second screen makes menus/dropdowns appear on the main screen (most annoying) - Sometimes at start Ready will not show because it is somewhere out of bounds of every screen. Can only be fixed by force closing the app, disconnect the external monitors and start Ready again and reconnect the screens
... View more
Status:
Implemented
Submitted on
06-14-2018
07:02 AM
Submitted by
gibsonman507
on
06-14-2018
07:02 AM
When cloning multiple test steps, there is no dialog to name each of the cloned test cases. ReadyAPI prepends "Copy of <teststep>" and this it becomes very tedious to rename each test step. I understand the purpose of prepending Copy of is so there's no duplicates within the same test case. My only request is that if the target test case for the cloned steps is different (therefore no need to make a unique identifier), that they simply clone as-is. IF there happens to be a test step with a conflict name in the target test case then it should be ok to auto prepend "Copy of". This would save lots of time when I clone 25 or so steps
... 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
See more ideas labeled with:
Different projects may require the same environments. It would be useful to clone them directly rather than recreating them all over again.
... View more
Status:
Implemented
Submitted on
11-28-2017
04:25 AM
Submitted by
bwennekes
on
11-28-2017
04:25 AM
To extend the composite project functionality and improve the way ReadyAPI’s XML-files can be version controlled I would like an option to save without property values. Ideally this option can be enabled/disabled for properties defined at Test Step, -Case, -Suite and -Project level with a checkbox. Currently there is only the option to ‘discard values on save’, which is only available on Test Step level. Discarding values on save can be quite cumbersome if you need the values making changes/corrections while still wanting to save often. This could mean that you need to rerun the whole project after a change is saved, which in my case may take more than half an hour. At this time I’m still using the ‘discard values on save’ option by lack of alternatives. This also means that all properties in the project must be defined at step level, the only place where this option is available. This in turn means we cannot use functionality like the ‘Run Test Case’ Test Step as this uses properties on Test Case level, which is a real shame. In my opinion just running and saving the ReadyAPI project should not change the project XML. As this currently does happen it creates hundreds of changes and merge conflicts without any functional changes in the ReadyAPI project.
... 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
See more ideas labeled with:
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
See more ideas labeled with:
Status:
New Idea
Submitted on
12-03-2021
08:36 AM
Submitted by
jfnumainville
on
12-03-2021
08:36 AM
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
See more ideas labeled with:
Status:
New Idea
Submitted on
09-08-2021
12:54 AM
Submitted by
DLeidelmeijer
on
09-08-2021
12:54 AM
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
See more ideas labeled with:
Status:
Accepted for Discussion
Submitted on
03-20-2021
04:30 AM
Submitted by
f4br3
on
03-20-2021
04:30 AM
Hello, everyone! Given the breakthrough and popularity of Apple's new silicon (M1), I think there should be an optimized version of ReadyAPI for this silicon, as it will obviously run faster than using Rosetta 2. Thanks!
... 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
Status:
Implemented
Submitted on
02-18-2021
11:00 AM
Submitted by
khanchett
on
02-18-2021
11:00 AM
Prior to this release test step assertions were always allowed to minimize, now it is not. I have groovy scripts and SOAP Request/Response xml that can be 100's or 10,000's of lines. * When my SOAP test step first opens up there is only 10 lines at a time that can display. * When I minimize the Assertion area I can get it to 15. Suggestions: * To collapse it on the right side so we can obtain the length of the screen. * Return it to allow the Assertions to collapse out of the way. Related suggestions: * For those of us that utilize ReadyAPI with Groovy and JDBC's more, it would be good to have better work area real estate when you push out these changes. * Also if a portrait screen was more user friendly I would use that more, unfortunately my home version (thanks to Covid) my portable monitor doesn't allow good screen resolutions. * Collapsing the left side and the bottom would be a fantastic option. Thank you!
... View more
Status:
Accepted for Discussion
Submitted on
07-08-2021
01:17 AM
Submitted by
AAB
on
07-08-2021
01:17 AM
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
See more ideas labeled with:
Hi. I have some eye issues and normally work with a dark background / high contrast in all apps. I use SoapUI daily and find it difficult to read with the default white background. I did a search on the forum and there was a previous request about a year ago in the SoapUI Pro area for this feature. The only response was that it was not supported. I would like to also request this feature. Thanks!
... View more