When the Scheduling server is not added during installation, the Configure button in Test Studio will be greyed out (disabled). It will be helpful to add some kind of tool tip or note about this.
The solution is to modify the existing installation of Test Studio and add the Scheduling Server feature to the installation.
We need to be able to verify the text in dialogs in different browsers.
The current solution is in code, but is not stable due to browser structure changes -> https://docs.telerik.com/teststudio/advanced-topics/coded-samples/html/verify-dialog-text-chrome
It will be helpful to have an element, which is defined based on another element. This is similar to chained find expression, but instead of defining the parent element with its find expression, add the ability to reference an already recorded element in the project as a parent one. Then add find expression for the child element.
Add the option to start quick execution of tests in Headless mode from Visual Studio.
Currently it is available from the Select Execution Browser window, but if you have selected a preferred browser this window is skipped.
Make it possible to add Keyboard Keypress steps against a target element from the Step Builder.
Currently the only way to add Keyboard Keypress actions is through a coded step that sends desktop actions.
After using Telerik Test Studio for a couple of yeas I have found a persistent problem. I have found myself renaming some objects in the Elements Repository because the auto-generated names didn't make any sense when they are used in coded step. The Element Repository engine that is responsible for maintaining optimizing the elements often consolidates pages and elements often causes some element objects to go "missing" because it has renamed these items back to some auto-generated form in most cases. Some cases I've had them disappear altogether because of our changing page definitions. I have still been trying to find what is the best way to implement pages within our given test environments.
The Step Builder and the Element repository optimizer is great for those who are less technically inclined (e.g. BQAs). However, I would like to request a mechanism for maintaining persistent names within the Element Repository. This is mainly because the loss of named elements used in coded steps. I have found myself resorting to the use of the XPath property to reference said object in coded step so that they, at least, compile.
When Daylight Savings Time ended on November 6, our scheduled tests started running an hour earlier than scheduled. I had to "edit" each schedule (without actually changing any settings) and save in order for the time in the "TimeToRun" setting in the job details file to adjust for the time change. It would be nice if this could happen automatically. Or maybe add a right-click option to for updating the time or something.
When there is a conflict in a source controlled project, Test Studio should output more details about the conflict. That will make it easier to track and resolve, as multiple users work in the same project.
Currently the output pane does not specify anything for the conflict.
Translator for Kendo Angular MaskedTextBox is currently missing and the <input> element is captured with its dynamic ID. As a result, we need to edit all recorded elements in that control manually.
Please add the necessary missing translator.
The element's find logic takes into consideration the parent element and its attributes. This does not apply to generating the element's name and makes it more difficult to distinguish between elements.
For example, if the application has two buttons under different parent elements with descriptive IDs, the recording will still capture the elements as "Span" and "Span0". Instead it could be using the parent element's ID to build the name.
Please add an interface that allows the user to resolve version control conflicts within Test Studio.
The BQAs in our group do not have a mechanism to resolve such conflicts (i.e. they do not have a copy of Visual Studio).
Http requests' responses with content-encoding type 'br' cannot be decoded in Test Studio load testing. This results in the inability of using these responses to generate dynamic targets to cover the proper load test run.
Workaround: Modify the traffic for a load user profile by removing the 'br' encoding type. A third party Chrome extension can be used for this modification.
Telerik does not support test studio assemblies in .net standard and does not have a test runner in .net core. Considering all of our Azure DevOps and container agents are running linux we will not be able to use the tool.
Please add this feature to your product.
I have a need to be able to test Text Content. I am currently testing content with exact, I am aware that there are a few other options available. One option that I do not see is one to test a range. For example the amount displayed is 4202.39; I would like to be able to check to ensure it is between 4202.38 and 4202.40. Is this a feature that is planned?