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
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:
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
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
Status:
New Idea
Submitted on
02-22-2022
05:49 AM
Submitted by
Inovalon-Tester
on
02-22-2022
05:49 AM
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
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
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:
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
See more ideas labeled with:
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:
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
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
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
Hi, The latest version of ReadyAPI 3.20.0 seems to fix encrypted properties being displayed as plain text in logs within the ReadyAPI software itself but this does not translate when running the project from Azure DevOps using the "ReadyAPI Test for Azure DevOps task" as encrypted properties are still being exposed there. 1. The project password for the task is in plain text - This property should be masked as anyone who views the task would be able to download and access the encrypted project and its properties. 2. Encrypted properties are displayed in the logs/requests as plain text The password has been encrypted in the custom properties using the "selected properties" project encryption . However, encyrpted properties are being shown in the task logs when a request that uses the properties fail or when logged using groovy script as plain text. This display of encrypted properties as plain text is unacceptable especially when creating production tests so it would be benefical if encyrpted properties are not exposed. Thanks, Kayleigh
... 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
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
I distinctly remember being able to use a 'Run From Here' option (context menu when right clicking a test case from the Test Suite summary screen i.e. the one where the bars show green and red when a test passes or fails). It seems to be gone in one of the last versions? I can see inside a Test case if you right mouse click on a test step you can select run from here. What happens to me is I have a suite with 20 cases and case 14 fails. I then inspect it and want to run case 15 onwards so in the past I would right mouse click this test case and choose Run From Here ...
... View more
See more ideas labeled with:
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:
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