I ran a few tests in a test list in Test Studio Mobile, and noticed, there is no report. It is just a test list which contains passed or failed test cases. Is there a reporting feature similar to the one for Web?
Also, I would like to export the results of the test list as a part of documentation, having run a set of test cases. Does the functionality exist in Test Studio Mobile? I did not find anything matching these requirements in the documentation.
How can I show a report of the tests which have run? And export them?
Please let me know
Currently the OAuth 2.0 support is limited to the following grant types: password, client_credentials and refresh_token.
It will be useful to add support for AuthorisationCode grant and Implicit grant as well.
Have been facing problem in performing data driven test for Kendo drop down list on web app but a lot of posts on forums suggested that issue is already fixed.
Only now to notice that the Kendo UI translators available in Test Studio now are for Angular.
But in our web app, Kendo for jQuery is used.
Would like to request for jQuery Kendo UI translator (jQuery Kendo Drop Down mostly used) as well so that we will be able to perform data driven selection on jQuery Kendo drop down list.
Ability to add multiple And/Or conditions in IF bracket
Recording using existing Chrome session is not available
Test Studio has support for Xamarin.Android however, I've seen that projects created with Xamarin.Forms are not fully supported. Is there any plan to have this compatibility in the future (ETA) ?
Export a test list result to HTML and open it.
When you hover over the actual and expected images, they are zoomed. They are not visible enough and as a result it is hard to analyze them.
Please improve their resolution and visibility.
Currently you can find the ImageOnFailure in the project's Results folder under the unique test list's result folder (something like "Failing Test 132106926993112448").
Add NTLM authentication in Test Studio for APIs or some kind of workaround.
Currently scheduling a test list with getting the latest server version of the project is only possible if the source control repository is of the TFS version control type (Team Foundation Version Control).
It will be very useful to add the same functionality for Git source controlled projects.
The step to verify an element for enabled/disabled step cannot be data-driven. The 'Verify element exists' also does not provide a binding option.
However, the 'Verify isVisible' step can be data driven with true/false values for the isVisible property.
It will be useful and helpful to unify the behavior and allow data binding for isEnabled and Exists verification steps.