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.
It would be useful to have the functionality to build the project from command line.
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.
The Application we are using stopped the support for IE. So I have to switch to chrome to be able to connect to the DOM window of TEST STUDIO. Inorder to connect to the browser, I have to use "Run - To here" option and then connect to the browser. Then I Navigate to the Page where I actually want to do the recording and debugging.
But in IE browser, I have the opened instance already and then I can connect the recorder wherever I want. This is more easier way of recording and debugging and save time.
So, Could you please consider this feedback and add the option for "Attach to chrome" browser. Refer to Screenshots..
Allow deserialization of dateTime values to strings instead of DateTime objects when extracting such with JSONPath.
When a dateTime value is returned in a JSON response ("2019-04-08T00:00:00") and a JSONPath expression is used to extract it from that response, Test Studio deserializes it to a DateTime object. This leads to losing its original format.
It will be useful to have the option to deserialize it in a plain string value.
Add Test As Step in Test Studio Mobile project. This will enable me to better organize the test scenarios and reuse already recorded tests.
The same feature is available in Web & Desktop projects.
We use the Telerik Testing Framework to run our pre-release tests on our AJAX.NET solution. The newest version contains the MultiColumnComboBox. The problem is, that the Testing Framework is missing a wrapper for the new Control (as the other controls have).
When using the visual studio plug-in, if you update coded files (anything ending in .tstest.cs), when you open your project back up in TS standalone IDE, the changes you made to any given coded file will not automatically be detected so you must open up every .tstest file corresponding to the .tstest.cs files you changed in visual studio, and only then will the IDE see the changes
In the case when a custom layout is set and the Project explorer pane is hidden on the left side of Test Studio project, there is no indication if a new test is added in the project.
It will be very helpful if the Project Explorer pops up to indicate that adding the test was successful.
We are using telerik testing framework for Automation testing. Currently we are executing our scripts in a client VM using TFS builds. Now we would like transform to Docker Execution. We couldn't get the direct solution from any forum for Telerik Testing framework and Docker integration. So please help us on identifying the docker image for Telerik testing framework, so that we will make use of it and we will create a container for the same to run our test scripts in docker vm. Any websites/links related to this topic would be helpful for us.
At this point it is possible to run a WPF application with arguments only as a workaround - starting a separate process in a coded step as given in this example. It would be more useful if this feature is implemented when configure the WPF app in the test.