I have a WPF UI that has multiple combo boxes, about a data grid. The Combo boxes are used to change what appears in the grid. When I am creating a test to verify the values of the items in the list, I am trying to get the hover menu to come up, but it quickly disappears when I try to get the menu item for a combobox item selected.
As a work around, I have been able to click Alt-Tab, and then go back to the screen, and that keeps the menu open for me to select an item, but I shouldn't have to do this.
Using the No Chrome Extension, the dialog window to upload a file doesn't open when running the test. I’m unable to give you access to my testing site, however, I used https://ps.uci.edu/~franklin/doc/file_upload.html to replicate the issue and supplied the Test studio projects for your review.
Chrome: Version 99.0.4844.51 (Official Build) (64-bit)
OS: Microsoft Windows 10 Enterprise
Version: 10.0.19044 Build 19044
I am using Test studio, and have developed my first project that verifies the UI in 8 languages. In the languages that have special characters, it is failing and reporting a value at the time of failure that does not exist. The value that was displayed truly matched the expected result. Many of my other strings that did not have special characters matched just fine. Not sure what is happening.
Text content of IPAddressData does not match!
Match Type: 'Exact'
Expected Result: 'Netzwerk nicht verfügbar'
Value at time of failure: 'Netzwerk nicht verfligbar'
As our team has grown, we have seen Test Studio record elements that already exists but with different naming conventions and under different pages.
Although I understand that much of the element class (pages.cs) is dynamically produced, I think it would benefit the end user to be able to drag/drop organizing the elements much like you can in other solutions. This would help the end user have a better organized and less chance for duplication/mess of elements.
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.
I have tried docking the Step Builder panel within Visual Studio various times and causes VS to crash every time.