Make "Run Test Case" properties multi line
When sending in data and returning data from a Run Test Case step, each property is single line. This is fine for simple values, but not particularly user-friendly for structured data like JSON. The properties could be multi line with the possibility of scrolling. Currently, I need to copy the data out and use a tool to reformat the data so it is readable. Current: A quick mock-up of what it might potentially look like : We use Run Test Case for things like putting a wrapper round an API call, (with error handling, retry, filtering, mapping functionality etc.) so if an API changes we only need to change it in one place rather than in each test case. We pass the whole JSON payload in and the whole JSON Response back. (If for some reason it would break existing functionality then have an "enable multi-line" checkbox) ALTERNATIVLY: If not possible, then a button at the end of the table row to open the value in a new window (similar to a the Groovy Script run result-output):
Make Smart Assertion more useful with added features
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.
Manage the projectVersion field in "Setting.xml" , so it doesn't update with every save or reload
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.Randomly generated values in requests and other ReadyAPI functions
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.Add a Regular Expression pattern to a String Generator
Current state Currently, the String generator allows to specify the length of the string and the string contents by character categories: Letters–By default, this check box is selected. Digits–By default, this check box is selected. Spaces–By default, this check box is selected. Punctuation marks–By default, this check box is selected. The docs are here https://support.smartbear.com/readyapi/docs/testing/data-driven/types/generator/string.html. Proposal However, there are cases which need more precise string format. Regular expression would allow an elegant way to define the format. I suggest to add an option to set a regular expression pattern. The String generator would follow the regex pattern instead of string length and the above mentioned character categories.
Don't prepend "Copy of" if the target testcase is different
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 Iclone 25 or so steps
Saving without property values
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.
Folder Structure | Needed asap!
rorySB We as a big company need a folderstructure feature. We need to logical group testsuites! Our existing Testframework (Playwright) with Typescript Code is built like this: So we have API Auth. Tests Ressource Userstories (Testsuite) Mapping Sheet Tests(Testsuite) Failure Retests(Testsuite) Ressource Userstories(Testsuite) Mapping Sheet Tests(Testsuite) Failure Retests(Testsuite) Ressource Userstories(Testsuite) Mapping Sheet Tests(Testsuite) Failure Retests(Testsuite) This structure we cannot create with ReadyAPI We need this feature asap because otherwise it could be messy without folders. So pls pack this feat request in your next sprint! Best regards Kranael
Multiple monitor support
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 screensDark Theme for SoapUI in ReadyAPI
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!Smart assertion: ONLY populate FAILED assertion from received data
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.Intellisense on custom groovy library
Can we, and if so how, use something like intellisense on a custom groovy library? So if we have created some utility functions and keep them in a script folder, or library, can we then reference those scripts and their methods intelligently from a groovy test step?Enabling OAuth2 for Kafka topics
It would really be helpful if OAuth2 authentication would be enabled for Kafka topics just like for Rest APIs. Tokens would be dynamicallygenerated 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)Linting or automatic code checking in ReadyAPI
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 herehttps://community.smartbear.com/t5/API-Functional-Security-Testing/Linting-or-automatic-code-checking-in-ReadyAPI/m-p/208439#M47532
Allow configuration for wiki/text renderer for Test Steps/Details
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.Script library interoperability, javaDoc, refactoring, search & autocomplete in all scripts
I'm sorry, but to me the idea mentioned Intellisense-on-custom-groovy-librarybyrunzTHalmost 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.Do not remove property when populating new values in Smart Assertion
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.
ReadyApi 2.0 - GetData resizeable
With the release of ReadyApi 2.0 GetData behavior was changed and we are NOT impressed. Font size is set and unchangeable Column width is set and unchangeable This means that ANY TestSuite, TestCase etc. with names longer than 16 characters all look a like, making it impossible to be efficient as new functionality forces us to MouseOver to be able to find the correct TestCase name. Please at least make the GetData Columns resiazeable, so we can see the names of our TestSuites and TestCases again! See attached file.Ready API 3.6.0 Allow for Assertions to be minimized - NEED MORE SCREEN SPACE
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!Add an event for Report post-processing
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 toextend 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 arethe 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.
Smart Assertion Conditions NOT Matches Regex
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) ?!?!ReadyAPI 2.5.0 moved the soap/rest request run button's position - Please put it back on the left
Current Change: In ReadyAPI 2.5.0, the soap and rest request run button, and for test steps Add Assertion button were tweaked to make them more prominent (they now include text labels). This itself is fine. However, as part of this change the position of the buttons was also moved. They're now on the right-side of the destination URI instead of the left side. Request: Please put the buttons back to the left-hand side of the URI. Reasoning for it's usefulness: 1. It's inconsistent design. The run button was ONLY moved to the right side for request test steps and operations. However, test cases, test suites, and JDBC test steps all still have the play button on the left-hand side. This breaks the consistency of the run button placement--people will now sometimes have to go to the left to run, and sometimes go to the right, all depending on what's being run. 2. Long-term users are also extremely used to the run button being on the left side, so it's a nuisance to have to keep moving over to the right side now to use it, when we habbitually go to the left-hand side first. 3. There was no need to move the buttons to the right--it didn't help increase the visibility of the buttons, and it doesn't provide any new benefits. 4. It also breaks certain usage patterns where I sometimes open a test request on a left pane, then one or two other validiton checks to the right of that, and they hit the run buttons from left to right while I'm trouble-shooting something. This works nicely when all buttons are placed on the left-hand side of their tabs.Mask Password in settings.xml file for Composite Projects
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.
Integrate ReadyAPI - Soapui Pro with Allure Reporting
Our organization would benefit greatly from integration with Allure Reporting. It would be great if SoapUi could allow for annotations, steps and links to be added directly in test case requests/steps that would then output the appropriate xml that generates the beautiful and detailed allure reports. http://allure.qatools.ru/Re-insert the Assertion HTTP
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!Add optional "Suite Group" level above Test Suites in the SoapUI hierarchy, for better organization
Enhancement Request: It would be useful if we add an extra "Suite Group", or "Suite Categories" level in the SoapUI test case hierarchy for organizing test suites. This would be a parent of Test Suite. This way you could collapse.expand categories of test suites. This should be an optional level, so that those who just want test suites wouldn't need to have the extra layer of categories. Reasoning for it's usefulness: Currently, in each project, we organize tests by test suite, and test case. There is no broader category than test suite. In a situation where you have multiple APIs that while might mostly be independent, but that do also have interaction with each other, it would be handy to have them all be in a single project. However, if each API itself needs several test suites for testing it, then having multiple APIs in a single project isn't great for organizing your test suites, since they're all in a flat structure at the test suite level. That's one reason for keeping the APIs in different projects, so that you can expand only the test suites for the given API, without seeing a bit list of all the other API's test suites. The most common usage for Suite Groups/Categories would likely be to organize test suites by each API in the project, but their would certainly be other categories that people would come up with.testrunner flag to specify which tags to ignore in test runs
Testrunner.sh currently supports the -T option, which allows users to specify which tagged test cases they want to run. However, there is not a flag that allows the user to specify which tags to ignore in your test run. For example, if I tagged test cases with "prototype" I could run only those tests with that specific tag using -T"TestCase prototype". However, if I wanted to run all tests but exclude the prototype tags I currently don't have the ability to do that. Maybe a new tag, or addition of ! into the flag would work? Ex: -T"TestCase !prototype" <----- where ! prefix specifies not to run tests with prototype flag This could even be expanded further where the -T option would support both inclusive and exclusive tags. Ex: -T"TestCase prototype !ignorethese" <---- run all tests that have the prototype flag, but don't run those that have ignorethese flagGeneric assertion.
It will be nice to have the option to set generic assertion for all the API request in the project , or to select some of the APEs should have the same assertion . meaning of generic assertion - The user will create the assertion and will have the option to set it the over API requests. Motivation - I have hundreds of API requests, more then have of them have the same assertion ,so i need to copy paste them one by one."Find" or "Search" feature accross multiple steps and places
I'm using ReadyAPI 2.5.0. Please implement a feature where I can search for text pieces accross all test steps, regardless their types. Right now I can do this by searching through the xml project files, but it's clearly not the best (or most friendly) option.Integration of Ready API with Zephyr Server
Hello, Just the way we have integration of Ready API to Zephyr cloud, Can we have the same integration wtih Zephyr Server too ? My organisation uses Zephyr server and we are very eagerly looking for the integration of zephyr with Ready API so that once Ready API project runs, Mapped zephyr test cases gets executed. Currently i see that we have that in Zephyr cloud and not on zephyr server. Can we have it on Zephyr server too. Thanks. We have a case 00397737 on the same.Cloning always adds 'Copy Of ..' to the name.
Any clone/move renames testcases/suites/steps to 'Copy of'. That is unnecessary if moved to a location, where no copies of them exists. Why not let me clone one or more teststeps, select a destination, and THEN check if one with the same name exists, and if it does, then let me decide on the name? It is especially annoying when cloning multiple objects, as you can't rename these before the cloning. And it gets even more annoying when you clone TestCases, as the new clone's file on the disk is then named 'Copy of'... ' and if you do not want mismatch between the TC name in ReadyAPi and on the disk (relevant when commiting to GitHub), you then have to manually rename the files on the disk afterwards.Feature for comparing datasources
Would be helpful & efficient if there was a simpler way to compare datasources, especially when working with large data sets where multiple calls to db/json wouldnt be practical. Scenario - Taking the results of a jdbc query & putting it into a datasource file. Then taking the results of a json query & putting that into a datasource file. Now compare the 2 datasource files to make sure the values match.Delete multiple selected request headers at once [BUG?]
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?The various panes and view windows should remember their sizes between sessions
In SoapUI 4.x, the navigation pane used to rememer it's last saved width between sessions. However, Ready! API does not remember this type of sizing information--every time you restart the app, the pans are back to their default sizes. Please enhance Ready! API so that all of the panes and view windows remember their last sizes. Everything is resizable, but it's a waste of time to have to keep manually re-sizing things because the application doesn't remember the settings.Enable SoapUI tests to call test cases in other projects
AFAIK for SoapUI versions up to 1.8.0,the calltestcase step only supports calling test cases within the same project. We have hundreds ofutility test cases in a large project with~1000application level test cases that use them. We also have another projectcontainingtests that need to call the same utility test cases. Currently we have tomaintain two copies of the utility test cases because the second project cannot call into the first. Instead, we would like to haveone SoapUIproject containing the utility test cases, and multiple otherprojects containing the application level test cases that call into the utility tests. Then we would not need multiple copies of theutility test cases, which is a maintenance headache. So we'd like to request a SoapUI enhancement to supportcalling test cases in other projects. That wouldreduce our maintenance efforts considerably.Show test steps also in JUnit report
Provide an option to also list the Test Steps within each Test Case in the JUnit report. Or provide a way to drill down on each Test Case if needed, by default it can still only show Test Case results. This will be greatly benefit for reporting under a Continuous Integration system.Make intellisence more intelligent in Groovy
On writing my code in Groovy I've noticed that the intellisence doesn't always have all the authorised objects/classes/... in it. e.g. I wanted to catch a node difference and tell the script that it needed to add a particular string when not found. On autocompletion of the intellisence the "is AllWhiteSpace" was not present. I had that in version 2.6.0 and also now in version 2.7.0. It would be great if Groovy script handles a lot more like C# intellisence.The capability to abort entire test execution through groovy
It would be beneficial to be able to abort an entire test execution gracefully through groovy. In my case I have an async operation that I kick off, delay a small period, check the status then iterate around that for a defined number of retries before deeming it a pass/fail. In certain cases it does not make sense for me to continue the test suite/entire test run in certain circumstances and I'd like to be able to issue an abort through groovy in this situation. Hopefully feature request gains traction with community. Thanks in advance. Ken.Make it possible to stop groovy script execution
For now there is no possible way to stop a groovy script from executing. If you create an infinite loop for example the application will crash in no time giving you no other option but to stop ReadyApi and start it all over again. This happened to me a few times and it's pretty annoying.Make it easier to tell if a test is running, and if so, which one
If I walk up to a workstation that has Ready!API up, I can't readily tell if a test package, suite, case, or step is in the middle of running, let alone which one is running. If something is executing, it should be glaringly obvious on the screen no matter which other item somebody has selected to look at, and it should be easy to tell what is running, and where it is in its sequence. I'm using Ready!API 1.8.0ENH: Repeat the HTTP/REST request for n times with specified delay between each trials until passed
Requesting for an enhancement to repeat the every HTTP/REST request for n times with specified delay between each trials until it passes its assertions. We are facing a problem in our testing while using two web interfaces. The first REST send a request to second HTTP/REST service which will take some time (Not sure, it may be from 60secs to 300secs anywhere). With a hard coded delay, it was very tough and wasting lot of time for testing. With this feature, it saves lot of time and effort. I knew this can be done through conditional step, but it has so much work involved with each step. BTW, basic behavior of any HTT/REST request should not change by default. it should behave like as usual now. One more this is, it is test step level feature.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
ReadyAPI Feature Requests
376 Posts
