ReadyAPI Feature Requests

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

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

Right now, JUNIT reports are not modifiable at all. They are important when comes to running test cases via some CI and host result/report at a url. JUNIT reports are so simple and do not give information about the REQEST/RESPONSE  of a failed step to actually look at the reason why the test cases failed on the test server which might run successfully on local. Across various communities, I see that this feature is required by most of the users, a lot of discussion around it, and the way suggested is via maven project which seems to put more effort than writing test cases. ... 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

For the metricReport, could display time Taken from big number of ms to display make sense of format. In the generate report for overview section, it has time taken number, that displays a huge number is millisecond. not make sense people to understand how long it takes to run the whole test till the manually calculate use math. in the overview section, better convert to hour, min, sec and ms.     ... View more

Hello, I am using the function to compare test runs in "Performance Tests" under the "Statistics" section. I have configured a lot of charts and I want to output them as a printable report. The diagram does not look nice because the generated document has portrait orientation and the diagram is compressed. There is no way to change the orientation to landscape. The page orientation landscape gives the diagrams more space. The extra space stretches the diagram. The stretching will make the diagram easier to read. ... View more

In the Statistics view of a deployed Virtual Service in the VirtServer Web Console, there is an historical graph of received traffic, with a 24 and 48 hour option.   We need to be able to look at a longer history for the service and would like a '1 week', '2 week', '1 month' and 'lifetime' view of the historical data if possible. Looking at the underlying VirtServer api, the v1.2/statistics/<deploymentID> call has at least 2 weeks of data provided the service has been running that long, so it would seem to only be a matter of adding additional entries into the Dropdown to query for the appropriate time ranges and rescaling the graph. ... View more

We would love to have ability to generate documentation from Test Suite / Case descriptions for the whole project in a desired format - word / pdf / html. It would also be nice if there was a way to format the description text and link other test cases / suites and use regular hyperlinks as well. ... View more

Virt Server User Admin GUI is currently missing and would be required for proper management of users when they exceed the number of about 10-20.  This feels like a hygiene factor and industry standard and we hope that this is in the pipeline.  ... View more

Virt Server requires a Single Sign-On functionality. It seems like a hygiene factor and business standard. If we can enable SSO then we will be one step closer to onboarding users and reaping the benefits of API virtualization for IKEA.  ... View more

As time progresses and more and more people virtualize API:s we would like the opportunity to expose the listing of those virtualizations for anyone. Let’s refer to it as a “Virtual Service Library” for now. We hope that this is in the pipeline of Service V Pro. ... View more

Generally, once you find SQL Injection or Cross Site Scripting for a parameter, you don't need to know the hundreds of other exploit strings that also worked. The important information for the developers is that parameter x has Cross Site Scripting vulnerabilities or stack trace errors. So a table with 2 columns (scan type, issue type)  that had a row for every distinct combination of scan type (e.g. SQL injection) and issue type 'sensitive data returned' or 'stack trace' would be very useful. If some requests worked and some failed the developers can always look at the report for the specific strings, but generally if you are not validating or escaping input, the specific strings that caused the issue don't matter.  ... View more

The Secure test reports can be hunderds of pages. It would be useful to have a table of contents with clickable links to useful sections, like the start of the issues for each scan type. ... View more